4 ms·
Really? I quite like them. I did get used to them in C# first, though. What would you have preferred?
by dvlsg 8y ago
Really? I quite like them. I did get used to them in C# first, though. What would you have preferred?
- irrational 8y agoI would have preferred a word. const my_arrow_function = arrow_function(){} arrow_function my_arrow_function(){} arrow_function(){}
- warty 8y agoIn older C#, that would be delegate: delegate(int x){ return 10; } (But yeah, nowadays that would be:) (int x) => 10
- mattbierner 8y 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