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.
Ha! To debug these, I tend to manually desugar until it's obvious.
I certainly hope not!
That would be helpful yes. But why not ‘for { .. } as[T]’ ? That would look neater (imho)
I'm not so sure. Where does the `yield` go relative to `as`, and why introduce another keyword? Appending the type constructor immediately after the `for` is akin to explicitly specifying the type parameter to a method.
Nja, not sure it is worth it as it makes the language more complicated with optional parameter. Opposite of one of the main goal of Dotty.
But don't you think there's plenty more complexity in an error message that tells you the opposite of what you want to be told (as I tried to show in my second tweet)?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
