Skip to content

Don't force LazyRefs when computing isProvisional #4082

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 1 commit into from
Mar 8, 2018

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Mar 8, 2018

I saw errors of recursive evaluation of LazyRefs in the IDE which were caused by
the fact that isProvisional forced their computation. It should not do that.
It now treats all uncompleted LazyRefs as provisional.

I saw errors of recursive evaluation of LazyRefs in the IDE which were caused by
the fact that `isProvisional` forced their computation. It should not do that.
It now treats all uncompleted LazyRefs as provisional.
val uniqId = {
nextId = nextId + 1
// // debug only: a unique identifier for a type
// val uniqId = {
Copy link
Member

Choose a reason for hiding this comment

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

Why did this get turned off?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's a field in every type, and we don't need it - it's used nowhere.

@smarter smarter merged commit e531634 into scala:master Mar 8, 2018
@Blaisorblade Blaisorblade deleted the fix-isProvisional branch March 8, 2018 19:50
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.

2 participants