You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rewrite any of our case classes that inherit (even indirectly) from Proxy
not use any library case classes that have Proxy in their inheritance tree
It has made using case classes a unsafe thing to do unless you are sure nothing they inherit from has Proxy, or will ever have Proxy, in its inheritance tree. What's worse is that this problem is causing our code to fail at runtime in very unexpected ways. If this behaviour is by design the least I would expect is some compiler warnings.
Thanks
The text was updated successfully, but these errors were encountered:
David Corcoran (corcorda) said:
Hi Paul. You fixed this a while ago but the 'Fix Version' is still None. Is that correct? Has this not be included in a release? Thanks
@paulp said:
It hasn't been in a released version yet. It should have said "unreleased 2.10" already; I backported it to 2.9.x since you brought it up, so now it will be in 2.9.3 as well.
In Scala 2.9 a case class is not equal to itself (even the same instance) if it inherits from Proxy. In Scala 2.8 this is not the case.
The discussion here describes it:
http://stackoverflow.com/questions/6667654/case-classes-and-proxy-behaviour-in-scala-2-9
This is causing us huge trouble as we have to:
It has made using case classes a unsafe thing to do unless you are sure nothing they inherit from has Proxy, or will ever have Proxy, in its inheritance tree. What's worse is that this problem is causing our code to fail at runtime in very unexpected ways. If this behaviour is by design the least I would expect is some compiler warnings.
Thanks
The text was updated successfully, but these errors were encountered: