4 ms·
1) you are wrong: https://gist.github.com/kaseyjunk/d58f00a4b1865feb94cc https://gist.github.com/kaseyjunk/d58f00a4b1865feb94cc No highlighting that helps. 2
by kasey_junk 12y ago
1) you are wrong:
https://gist.github.com/kaseyjunk/d58f00a4b1865feb94cc https://gist.github.com/kaseyjunk/d58f00a4b1865feb94cc
No highlighting that helps.
2) You've moved the goalposts. The original parent said that he found the call syntax confusing, you responded by saying your heavyweight IDE prevents that confusion from happening, and I pointed out the tradeoff required for that. Now you've gone back and just said it isn't confusing and that it is something you have "to work out".
The fact is, some Scala developers find the call syntax confusing and some Scala developers read Scala code in editors that do not have the power to help them suss that out. That is a cost to the flexibility in call syntax. Is that cost worth it? For some people yes, for some no, but don't deny the cost.
- lmm 12y ago1) Fair enough; I'm very surprised, and will take a look at fixing that. 2) I didn't mean for the user to work it out, I meant that a simplistic highlighting script should be capable of it.