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
Seeing that a method interacts w/ the database, or can potentially fire missiles, is as important at the call-site, as its definition. And if we want context, if we want DI, Scala also has a true and tried way of doing it, which is OOP classes, closures on steroids.
This is less true in Scala 3 where context (i.e. givens) must be explicitly imported. You do that once for a particular scope, and that sets your context, which you accept for every method call in that scope.
Let's ignore firing nuclear missiles for now, but a beginner learning the language who doesn't care how many calls are being make to the database would benefit from being able to read the code without worrying about when the database connection is used. The code is more readable.
Or consider a logger parameter. If you have to explicitly pass a logger object to every method that uses it (probably all of them) that's a death-by-a-thousand-papercuts level of distraction in every expression making the important parameters harder to see.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
