5 ms·
Gluon recently added implicit arguments with the latest release (see http://marwes.github.io/2018/06/19/gluon-0.8.html http://marwes.github.io/2018/06/19/gluon-
by jdreaver 8y ago
Gluon recently added implicit arguments with the latest release (see http://marwes.github.io/2018/06/19/gluon-0.8.html http://marwes.github.io/2018/06/19/gluon-0.8.html). In spirit it is like modular implicits (https://arxiv.org/pdf/1512.01895.pdf https://arxiv.org/pdf/1512.01895.pdf). This is really exciting because modular implicits represent a pragmatic balance between the flexibility of ML modules and the convenient overloading of type classes.
Another cool feature of Gluon is modules are basically just records. This is a strict improvement over ML modules in my opinion. (See http://gluon-lang.org/book/modules.html http://gluon-lang.org/book/modules.html)
Congrats on the recent release!
- MrBuddyCasino 8y ago> implicit arguments Because it worked so well in Scala?
- tutanchamun 8y agoWhat's the problem of implicit arguments in scala? I can see why implicit conversions can be a problem but aren't implicit arguments required for typeclasses and other nice features?
- pas 8y agoWhat's your opinion of Odersky's scala3 implicit plan?
- MrBuddyCasino 8y agoI'm not very familiar with Scala3, but as far as I'm aware implicits are still a core part of the language? Let me put it like this: I recently applied to two high-profile startups with experienced technical leadership, and they both explicitly asked me if I was a Scala fan. They weren't and made bad experience in the past regarding productivity due to complexity, tooling and developer onboarding, which unfortunately matches my experience. There is some good stuff for certain niches (Akka, Spark etc.), but otherwise I feel like Kotlin is winning.
- jdreaver 8y agoYou should read the paper :) Modular implicits are not the same as Scala implicit arguments. Gluon probably just chose the name "implicit arguments" because it corresponds better to their variation on modular implicits.