fix(reactivity): align the get/set operations to ECMA spec #3025
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.
close: #3024
I would say that this PR introduces expensive operations(
Reflect.getOwnPropertyDescriptor
?), but it aligns with the ECMA spec. For issue #3024, I think it's also a good way to document it so that expensive operations can be avoided.Related specs: https://www.ecma-international.org/ecma-262/11.0/index.html#sec-invariants-of-the-essential-internal-methods
The main part is:
[[Get]] ( P, Receiver )
[[Set]] ( P, V, Receiver )