News for hackers. Stuff that matters.
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.
Re:The Future of Standard ML (2013) [pdf] by rvense on Thursday July 14, 2016 @09:24PM (#12098419)
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 b
Re:The Future of Standard ML (2013) [pdf] by jfb on Thursday July 14, 2016 @09:45PM (#12098483)
What? 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.
Re:The Future of Standard ML (2013) [pdf] by snoman on Friday July 15, 2016 @02:12AM (#12099222)
Don't know Scala but why wouldn't it be

a.append(l).append(b)

?

Re:The Future of Standard ML (2013) [pdf] by rvense on Friday July 15, 2016 @06:00AM (#12099860)
That would only work if a was itself a list..