Re:The Future of Standard ML (2013) [pdf]
by jfb on Thursday July 14, 2016 @08:55PM
(#12098326)
I can see the argument for terseness in source, particularly in domains where the terseness in code reflects well-understood shorthand in the actual problem space. But stuff like that makes me itch, to be honest.
[ Parent
| on HN ]
The alternative would be something like
l.prepend(a).append(b)
Horrible. Ghastly. Can't see anybody tolerating a language that looked like that.. /s
Re:The Future of Standard ML (2013) [pdf]
by yawaramin on Thursday July 14, 2016 @10:19PM
(#12098590)
It gets even worse. Because Scala has infix syntax for method calls, you can do
l prepend a append bWhat? Mutating a list? DISGUSTING!
Re:The Future of Standard ML (2013) [pdf]
by speedkills on Thursday July 14, 2016 @10:33PM
(#12098633)
It's not mutating, its returning a new list with elements prepended and appended.
Don't know Scala but why wouldn't it be
a.append(l).append(b)
?