Eliminate an unsafe optimization of list matching #8189
Merged
Conversation
This file contains 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
In rare circumstances, the compiler could do an unsafe rewrite of
list matching operations. For example:
[PrevRow | _] = Rows,
[_ | PrevRowT] = PrevRow,
. . .
Provided that the type analysis pass had figured out that `Rows` is
always a list of at least two elements, the compiler would essentially
rewrite the code to:
[PrevRow | PrevRowT] = Rows,
. . .
Fixes erlang#8187
bjorng
added
team:VM
CT Test Results 2 files 324 suites 10m 17s ⏱️ Results for commit f441ac9. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
kikofernandez
approved these changes
Feb 26, 2024
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.
In rare circumstances, the compiler could do an unsafe rewrite of list matching operations. For example:
Provided that the type analysis pass had figured out that
Rowsis always a list of at least two elements, the compiler would essentially rewrite the code to:Fixes #8187