You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
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`.
Compare that to a "normal" (non-context) function parameter, where one user will write `{ r => ... }`, another will write `{ req => ... }` and another will write `{ httpRequest => ... }`. Any user reading that code needs to learn the parameter name for each use site.
Just found a good use case for context function at work, but I will have to do it with scala 2 syntax for a bit before pushing the team to upgrade to scala 3.
Luckily you still have the { implicit foo => ... } syntax in Scala 2, so in theory, that part of your upgrade should be just a matter of removing the lambda variable.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
