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
"Only sealed abstract classes that provide implicit instances to companion objects are allowed here, since they don't affect usage outside of the file."
The text was updated successfully, but these errors were encountered:
When concrete methods are being moved between abstract sealed classes whose usage is in a single inheritance hierarchy, the change should be deemed binary compatible.
E.g.
sealedabstractclassA {defa=1 }
sealedabstractclassBextendsAclassCextendsB//only usage of A and B
If you move def a = 1 to B it should be deemed as binary compatible.
adriaanm
changed the title
Ignore sealed abstract classes that can't affect usages in other compilation units
Allow moving method within sealed abstract class hierarchy
Aug 3, 2018
dwijnand
changed the title
Allow moving method within sealed abstract class hierarchy
False positive moving methods within sealed abstract class hierarchy
Nov 19, 2019
Needs clarification: typelevel/cats#2335 (comment)
"Only sealed abstract classes that provide implicit instances to companion objects are allowed here, since they don't affect usage outside of the file."
The text was updated successfully, but these errors were encountered: