4 ms·
I loathe implicits with the heat of a thousand suns. I mean, I love implicit conversions for easy addition of syntactic sugar, but they should be used very spar
by EdwardDiego 13y ago
I loathe implicits with the heat of a thousand suns. I mean, I love implicit conversions for easy addition of syntactic sugar, but they should be used very sparingly.
It could just be my indoctrination into Python's more of Explicit Over Implicit, but I hate it when things mysteriously turn into things or get passed as implicit arguments because something was in scope. My most hated form is nested implicit conversions, it kills code readability immediately if you can't figure out what type or object actually got passed in. And I'm using IDEA btw, so about as much tooling on hand to interpret said code as I'm likely to get.
Of course, you don't have to use implicits, but so much idiomatic Scala code (if I can interpret Typesafe's output to indicate idiomatic Scala) uses it, so I guess it's here to stay.
I do love the pattern matching though, especially when it's destructuring.
- eklavya 13y agoYou do know implicit conversions are marked by underlines, (both in IDEA and Eclipse) right?
- EdwardDiego 13y agoYes, but when an implicit conversion has been applied to an implicit conversion has been applied to a... ...well, underlining it helps but can't convey all that has gone on.