3 ms·
I understand the distinction and don't like implicit parameters. Coming from Clojure, one could say that the "use" keyword shares a lot of the same pitfalls as
by christophilus 9y ago
I understand the distinction and don't like implicit parameters.
Coming from Clojure, one could say that the "use" keyword shares a lot of the same pitfalls as implicit parameters, in that you are introducing values into your namespace which have not explicitly been referenced or scoped.
In Clojure, I choose "require" instead of "use" because "use" introduces too much ambiguity. The "use" statement in Clojure consistently makes code harder to read (for me), and I suspect the same is true of Scala's implicit parameters.
[Edit: Rails is another great example of implicit parameters run amok. Needless to say, I'm not a Rails fan.]