Skip to content

Fix #3606: Fix unpickling recursive types #3622

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

Merged
merged 3 commits into from
Dec 20, 2017

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Dec 2, 2017

Since recursive types register themselves, we should test the registry before
building them again. Otherwise, a repeated read (for whatever reason) will
install a new recursive type, but then any nested SHARED node of a reference
to the binder will pick up the reference to the old type.

Based on #3621 and #3602.

@odersky odersky requested a review from nicolasstucki December 2, 2017 14:15
Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Commit Messages

We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).

Please stick to these guidelines for commit messages:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Added" instead of "Add")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

Tasty needs to know about outer selections as separate trees. So instead of
exposing a name for outer selects we expose a tree format. This allows us to
store the type of tree selection in the tree, which got lost before.

Also: Change format of NAMEDarg to no longer require a length.
Since recursive types register themselves, we should test the registry before
building them again. Otherwise, a repeated read (for whatever reason) will
install a new recursive type, but then any nested SHARED node of a reference
to the binder will pick up the reference to the old type.
@@ -1443,7 +1443,8 @@ object SymDenotations {
onBehalf.signalProvisional()
val builder = new BaseDataBuilder
for (p <- classParents) {
assert(p.typeSymbol.isClass, s"$this has non-class parent: $p")
if (p.typeSymbol.isClass) builder.addAll(p.typeSymbol.asClass.baseClasses)
else assert(ctx.mode.is(Mode.Interactive), s"$this has non-class parent: $p")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is fixed with this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was an IDE hardening tweak.

@odersky odersky merged commit 13e879c into scala:master Dec 20, 2017
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.

3 participants