Editorial: Correct usage of 'Let'/'Set' in algorithms #3131
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.
There are some algorithms where same variable is defined twice:
Both algorithms define a (target) variable at the beginning, thus the declarations afterward are redeclaration which should be fixed.
Please note that this is a continuation of PR #2365.
HasCallInTailPosition, CaseBlock
The variable has is defined in step 1. However, in steps 2, 4, and 6, there may be duplication since let is used to modify the value instead of set.
Evaluation, YieldExpression
The variable value is defined in step 3. However, in step 7.c.iii.1, value may be redefined since the spec uses Let to change the value, rather than Set. This potential redefinition may also occur in step 7.c.viii.1.