Skip to content

Fix a typo that caused unnecessary cache invalidation #4259

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
Apr 15, 2018

Conversation

smarter
Copy link
Member

@smarter smarter commented Apr 5, 2018

No description provided.

@smarter
Copy link
Member Author

smarter commented Apr 5, 2018

test performance please

@dottybot
Copy link
Member

dottybot commented Apr 5, 2018

performance test scheduled: 4 job(s) in queue, 1 running.

This uncovered a missing case for changeParents
@smarter
Copy link
Member Author

smarter commented Apr 5, 2018

retest performance please

@dottybot
Copy link
Member

dottybot commented Apr 5, 2018

performance test scheduled: 3 job(s) in queue, 1 running.

@smarter smarter requested a review from odersky April 6, 2018 00:12
@smarter
Copy link
Member Author

smarter commented Apr 6, 2018

There's many cases where we call copySymDenotation without calling copyCaches, but assuming that we have set changeMembers/changeParents correctly in all phase, couldn't we always copy the caches when copySymDenotation is called?

@dottybot
Copy link
Member

dottybot commented Apr 6, 2018

Performance test finished successfully:

Visit http://dotty-bench.epfl.ch/4259/ to see the changes.

Benchmarks is based on merging with master (e0ef928)

@odersky odersky merged commit 4ded045 into scala:master Apr 15, 2018
@allanrenucci allanrenucci deleted the fix/sameParents branch April 15, 2018 18:37
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