Always request a new tree-shaking pass when deoptimizations are performed#4111
Merged
Merged
Conversation
… are first included
Closed
Thank you for your contribution! ❤️You can try out this pull request locally by installing Rollup via npm install rollup/rollup#gh-4097-request-treeshaking-pass-on-deoptor load it into the REPL: |
Codecov Report
@@ Coverage Diff @@
## master #4111 +/- ##
=======================================
Coverage 98.08% 98.08%
=======================================
Files 201 201
Lines 7039 7056 +17
Branches 2061 2061
=======================================
+ Hits 6904 6921 +17
Misses 64 64
Partials 71 71
Continue to review full report at Codecov.
|
9 tasks
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
… are first included
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Resolves #4097
Description
Now that all deoptimizations happen lazily, there is a now class of issues that can arise, notably when during a tree-shaking pass, no new variables are included but some nodes perform deoptimizations for the first time.
Previously, new passes were only triggered when new variables were included. This has been changed to also trigger new passes when deoptimizations are applied.