3 ms·
I made the same type of arguments about fat arrows but everyone told me to stop whining and I'd get used to it. Years later fat arrows still feel like a bad syn
by irrational 9y ago
I made the same type of arguments about fat arrows but everyone told me to stop whining and I'd get used to it. Years later fat arrows still feel like a bad syntax choice.
- strainer 9y agoAnd they are ready to overload them here :/
- dvlsg 9y agoReally? I quite like them. I did get used to them in C# first, though. What would you have preferred?
- irrational 9y agoI would have preferred a word. const my_arrow_function = arrow_function(){} arrow_function my_arrow_function(){} arrow_function(){}
- warty 9y agoIn older C#, that would be delegate: delegate(int x){ return 10; } (But yeah, nowadays that would be:) (int x) => 10
- mattbierner 9y agoFrom a language design perspective, fat arrows make parsing unnecessarily complicated because you cannot distinguish "(a, b, c)" from "(a, b, c) => ..." without looking ahead or backtracking. Certainly not difficult to solve, but this choice makes extending arrow syntax more difficult and the fact that a production called `CoverParenthesizedExpressionAndArrowParameterList` exists in the language grammar is a pretty ugly IMO