Do not trigger resolution cache invalidation if watch is triggered by program file emit#21149
Merged
Conversation
…d hence invoking recompile
…f program emit files Handles #20934
mhegazy
approved these changes
Jan 11, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If the number of source files in the resolution cache are more than maxNumberOfFilesToIterateForInvalidation (which is 256) then any file addition/removal triggers the new program creation to optimize for having to iterate through lot more resolutions.
This ensures that if file added/removed is from program emit, we ignore those and do not recompile the program
Fixes #20934