An interesting consequence of Scala 3's context functions is that since the parameter's name isn't chosen at the call site (it's implicit), it's often accessed using a helper method, and that method will have a consistent canonical name across codebases. That helps readability.
If a shorter name for `summon` could have been found, I might have preferred that, actually. I still use `summon` in place of named `using` parameters because it's more explicit about what it's doing, and means I can use context bounds.
-
-
I liked the initial proposal to rename `implicitly` to `the`. It seemed like at least for smaller projects you can avoid defining all these custom summon methods. But having short functions in global scope has drawbacks, I guess.
-
I was thinking about `the` when I wrote my last reply, but mostly because I hated it as the name of a thing! I'm fine with naming methods after nouns, verbs and prepositions in code... but an article just seemed wrong!
- Show replies
New conversation -
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.