Re:Towards Scala 3
by philipwhiuk on Friday April 20, 2018 @06:17PM
(#16888833)
> If you don't like them, why don't you add "Use of implicits forbidden" to your coding style guidelines, and check in code-reviews, and add a "grep implicit" check to your CI setup that refuses to commit Scala code with implicits?
Because Scala libraries that do useful stuff are infested with them. Akka loves the things.
> main complaint
They obscure complexity, pretending that complex stuff is simple. It makes simple stuff trivial but complex stuff harder.
Re:Towards Scala 3
by YorkshireSeason on Saturday April 21, 2018 @05:11AM
(#16890644)
> Akka loves the things.
So? Treat Akka as a black box. You can always explicitly pass implicit arguments.
Re:Towards Scala 3
by MrBuddyCasino on Saturday April 21, 2018 @10:21AM
(#16891512)
"If you don't like them, why don't you add "Use of implicits forbidden" to your coding style guidelines, and check in code-reviews, and add a "grep implicit" check to your CI setup that refuses to commit Scala code with implicits?"
Only someone who has never worked in a team before would suggest this.
If you don't like them, why don't you add "Use of implicits forbidden" to your coding style guidelines, and check in code-reviews, and add a "grep implicit" check to your CI setup that refuses to commit Scala code with implicits?
Let me paraphrase M. Odersky's PLDI 2017 keynote:
You can find it at https://www.youtube.com/watch?v=br6035SKu-0