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
A new error will occur with code like this: trait Foo(x: Int) trait Bar extends Foo // not allowed to extend Foo(0)! class Baz() extends Bar We are told that we need to explicitly specify the inheritance of Foo with its parameter, like so: class Baz() extends Bar, Foo(0)
Hoping that gets reverted
Really, why? Because it's performing a function too similar to `&` and `with`?
And something changed around self types. If X refers to Y members you can say: trait X { this: Y => … } but if X implements any of Y you must say: trait X extends Y { … }.
That's very interesting, and I never saw the relation ro self-types before, but it seems like "parameterless trait inheritance" is very much like a self-type, except that if the trait is parameterless anyway, it's inherited... Thanks for the hint!
I don't really understand the reason for trait parameters other then allowing context bounds / implicits on the type parameters. Also I was never find of extending case classes either. Something about it feels wrong. Like mixing types and values in the wrong way.
Would love to see a usecase that makes sense for this.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
