Editorial: make the order of parameters for class field AOs more consistent #2504
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.
Various of the abstract operations introduced in #1668 took their parameters in the order (key, object) or (key, object, value), rather than the prevailing convention of (object, key) or (object, key, value) respectively (as in Get, Set, etc). (Thanks to @devsnek for pointing this out.)
This PR swaps the order of the parameters for those methods to match the prior convention.