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
Here's a Scala 3 feature suggestion: I'd like to write for-comprehensions which know their generator type, like so: for[List] { x <- xs y <- ys } yield ... It would make it much easier to work out whether `xs` or `ys` is the wrong type.
What happens now: val xs: Option[Int] = … val ys: List[Int] = … for { x <- xs y <- ys } yield x + y error: type mismatch; found : List[Int] required: Option[?] y <- ys The error's misleading because the real mistake is in x <- xs, and it's the wrong way round.
YES! I've had so many stupid moments where I ended up with the wrong type because `xs` was a different type than I expected!
Yep. Me too. In my specific case, I often work in the same place in code with futures, event streams, and signals (event streams with caches). It's not difficult to mix them up.
Can you show a little code????
Agreed! And, this would also help those who are learning the language.
That could be useful.
Explicitly type all the things?
Optionally...
Ah interesting, OCaml has something like this now with its ‘let’ operators, they are defined typically in different modules for different types and you would locally open the appropriate module to use its ‘let’ operators. This indicating which type the expression should have
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
