Skip to content
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

Merged
merged 1 commit into from
Jun 8, 2019

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jun 8, 2019

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.

Reverts:
  Fix scala#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.
@anatoliykmetyuk
Copy link
Contributor

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?

@anatoliykmetyuk
Copy link
Contributor

@smarter would you know the answer?

@anatoliykmetyuk anatoliykmetyuk merged commit 2aad7b9 into scala:master Jun 8, 2019
@anatoliykmetyuk anatoliykmetyuk deleted the fix-print-pw branch June 8, 2019 17:07
@smarter
Copy link
Member

smarter commented Jun 8, 2019

It's not possible to overwrite maven artifacts, we'd need to publish an RC2 if we consider this critical enough.

@anatoliykmetyuk
Copy link
Contributor

I can rebase 0.16.x on top of master, change the baseVersion to 0.16.0-RC2 and tag it the same. This will give us 0.16.0-RC2 on maven. @odersky will that do?

@odersky
Copy link
Contributor Author

odersky commented Jun 8, 2019

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.

@odersky
Copy link
Contributor Author

odersky commented Jun 8, 2019

I can rebase 0.16.x on top of master, change the baseVersion to 0.16.0-RC2 and tag it the same. This will give us 0.16.0-RC2 on maven. @odersky will that do?

I believe that should work well, but I am not an expert on this. @smarter can you confirm this is OK?

@smarter
Copy link
Member

smarter commented Jun 8, 2019

Yes that's fine

@smarter
Copy link
Member

smarter commented Jun 8, 2019

Though you should merge master into 0.16.x, not rebase which would rewrite the public history

liufengyun added a commit to dotty-staging/dotty that referenced this pull request Jun 9, 2019
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.
@liufengyun liufengyun mentioned this pull request Jun 9, 2019
liufengyun added a commit to dotty-staging/dotty that referenced this pull request Jun 9, 2019
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

qualified private and protected not rendered by tree printers
3 participants