-
Notifications
You must be signed in to change notification settings - Fork 7
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
Ensure root is set in both worlds. #174
Conversation
(The assertion violation was silently ignored in a few test cases. As it is no longer needed, remove it.)
…hecker into issue-159-again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
withMostConvenientWorld.setRoot(root); | ||
} | ||
} | ||
settingRoot = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might have expected for this to appear inside the if
so that that block both sets to true
and sets to false
. That would also mean that, if someone tried to call setRoot
twice while a call was already active, then it would still be a no-op.
But I see no reason to think that the current code is a problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, definitely nicer in the block. I've moved the assignment.
I've confirmed that this fixes the crashes from my testing in the Google depot. |
…hecker into issue-159-again
Fixes #159, for real, hopefully.
This PR contains all changes in #173, so review and merge that first.