SIP proposal: uncurried update method was a mistake and should be deprecated
216 views
Skip to first unread message
Arno den Hartog
Dec 30, 2015, 11:16:16 PM12/30/15
to scala-debate
The current scalac implementation of the update method sugar only works correctly in the most basic cases.
I am arguing for an exactly-once-curried update method, more currying leads to intractable ambiguities.
I direct your attention to this here gist: https://gist.github.com/acdenhartog/a47fad6ebe8d32ff0ff5
This is not exactly the grand-vision sort of SIP proposal, more like the overdue housekeeping kind.
Also I have not read the Scala puzzlers yet, so I do not know if any of these issue are in there.
Best regards,
Arno
I am arguing for an exactly-once-curried update method, more currying leads to intractable ambiguities.
I direct your attention to this here gist: https://gist.github.com/acdenhartog/a47fad6ebe8d32ff0ff5
This is not exactly the grand-vision sort of SIP proposal, more like the overdue housekeeping kind.
Also I have not read the Scala puzzlers yet, so I do not know if any of these issue are in there.
Best regards,
Arno
Tongfei Chen
Jan 15, 2016, 2:52:43 PM1/15/16
to scala-debate
+1. This change would make NdArray update possible using the following syntax:
a(1, 2, ..., n) = x
Reply all
Reply to author
Forward
0 new messages