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
It would be safe to still generate the unapply and copy methods, but with a private modifier. They could be used / helpful from the class body, but wouldn't belong to the class public API, so couldn't break binary compatibility.
The text was updated successfully, but these errors were encountered:
This is a good idea. It would be great if we could tweak private to private[$package] so that library authors can still use unapply and copy internally inside their library if they want to.
It would be safe to still generate the
unapply
andcopy
methods, but with aprivate
modifier. They could be used / helpful from the class body, but wouldn't belong to the class public API, so couldn't break binary compatibility.The text was updated successfully, but these errors were encountered: