Jon Pretty

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.

For example, imagine an HTTP server's request handler is typed `Request ?=> Response`, so the request object is "given" within its body at the callsite. Defining, def request(using Request) = summon[Request] in the library means the request will always have the name `request`.

Either this or everything will have names summon[Blah]

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.