i guess i should explain exactly what my bad programming language is going for
i want to make a language supporting both FP-style (side-effect-free) functions and imperative-style (side-effectful)... uh... let's call them procedures
i would love to have currying and partial application and other such nice things, but there's some other stuff i would like too, so i gotta be careful about syntax so it can actually express stuff nicely
programming language design
@typhlosion study how the C++ Standard Template Library handles currying via std::bind, look at some code that uses it, and then realize that whatever you invent cannot possibly be worse than what people already use every goddamn day in this stupid industry