Questions about designing golfing languages
Examples
- How can I design versatile string slicing in my stack-based golfing language?
- In what way can I/O be designed so that it is mostly unnecessary within most programs, but still flexible?
Arguments
- For: foo
- Against: Questions of this kind more or less resemble discussions and as such are not good fit for the SE format.
