It shouldn't be unreasonable to assume that, val vector = List(1, 2, 3).to[Vector] vector(1) ought to be replaceable with, List(1, 2, 3).to[Vector](1) It can't right now, and I think this is a significant part of the reason why the abstraction of implicit parameters is leaky.
-
Show this thread
-
Note that the current proposal in Scala 3 is to make this work as I expected. If you wanted the old Scala 2 behavior, you would have to write, List(1, 2, 3).to[Vector].explicitly(1) I'm fine with that as a solution, but
@li_haoyi's proposal (in the GitHub thread) goes further.2 replies 0 retweets 3 likesShow this thread -
Replying to @propensive @li_haoyi
Can you share the link? I'd like to read more about this. Thanks :)
1 reply 0 retweets 0 likes
Replying to @francoeurdavid @li_haoyi
Jon Pretty Retweeted Jon Pretty
Sorry, it wasn't threaded!https://twitter.com/propensive/status/999994951462277122?s=19 …
Jon Pretty added,
Jon Pretty @propensive
Very interesting discussion going on about implicits in Scala 3 here: https://github.com/lampepfl/dotty/issues/1260#issuecomment-391774912 …—some good ideas from @li_haoyi & @odersky. I haven't picked a horse yet, but I really want to see it become impossible to accidentally supply an implicit parameter at a call site.
6:25 AM - 25 May 2018
from Milan, Lombardy
0 replies
1 retweet
2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.