I keep asking, without any good answer. Backward compatibility with bugs is such nonsense :(
-
-
AFAIK source incompatibility of non-experimental features would warrant an Epic increment.
1 reply 0 retweets 0 likes -
Replying to @viktorklang
.
@viktorklang@tpolecat@adelbertchang it could be source comp if case class implied final, & actually extending them is forbiden since 2.82 replies 0 retweets 0 likes -
1 reply 0 retweets 0 likes -
Replying to @viktorklang
.
@viktorklang@tpolecat@adelbertchang yes, it's possible but extending case class should not be done if you expect pattern matching to work1 reply 0 retweets 0 likes -
I'm not sure I understand your point then. It can't be made final because it would be source incompatible.
1 reply 0 retweets 0 likes -
is it still a source incompatibility if nobody use it and/or if only use cases are likelly bugs?
1 reply 0 retweets 0 likes -
if code which compiled fine before does not compile fine after, then the source is incompatible.
1 reply 0 retweets 0 likes -
even for bug correction ? Ok then. It won't be ever done :(
1 reply 0 retweets 0 likes -
I guess if the code wasn't ever supported by the language spec then it would be a slightly different story.
2 replies 0 retweets 0 likes
This was a feature for a couple of minor versions of Scala 2.5ish... but quickly disappeared.
-
-
Replying to @propensive @viktorklang and
Still my favorite example of extending case classes: https://github.com/lift/framework/blob/f6296ec60001ecf4eeaba475a9fe69e1217e5b90/core/common/src/main/scala/net/liftweb/common/Box.scala#L579 …
1 reply 0 retweets 1 like -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.