-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STOP THE PRESS - Fix privateWithin printing #6642
Conversation
0.16.0-RC1 is already in the Maven... Will force-pushing 0.16.0-RC1 tag again overwrite the maven artefacts? Will we need to remove the automatically created release from github releases? |
@smarter would you know the answer? |
It's not possible to overwrite maven artifacts, we'd need to publish an RC2 if we consider this critical enough. |
I can rebase 0.16.x on top of |
I believe it is critical. The problem is that right now, private def f ... prints private[<none>] def f ... That's not good for a first impression. |
Yes that's fine |
Though you should merge master into 0.16.x, not rebase which would rewrite the public history |
The issue in scala#6642 shows that errors may be latent in seemingly simple fixes if not tested, which can backlash us at critical moment.
The issue in scala#6642 shows that errors may be latent in seemingly simple fixes if not tested, which can backlash us at critical moment.
Reverts:
Fix #620: show privateWithin in tree printing (reverted from commit 8a7e01e)
The previous fix messed up printing of all private definitions that did not have a privateWithin.
We need to wait with the 0.16 release until this is merged.
Also, it would be good to add tests. I verified interactively that it does the right thing now, but am out of time to write a proper test.