Repository navigation
Fix repeated target evaluation in compound assignments - #45
Open
gabriel-andreescu wants to merge 1 commit into
Open
gabriel-andreescu wants to merge 1 commit into
gabriel-andreescu wants to merge 1 commit into
Conversation
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.
Compound assignments such as
values[NextIndex()] += 1callNextIndex()twice,so the read and write can target different elements. Member assignments such as
NextObject().Value += 1have the same problem.Capture the array reference and index, or member receiver, once and reuse them
for the read and write. This also keeps the target stable if the right-hand
expression changes it.
Checked generated PEX for Skyrim and Fallout 4, including struct members and
all five compound operators.
Fixes #11.