chore: tidy up each block compiler logic #12513
Merged
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.
per #12511, I intend to look into whether we can use compile-time analysis to determine the behaviour of each blocks. Just doing a little tidy-up before I get started:
node.context
being a destructured pattern has no bearing on whether the index should be reactiveeach_type
toflags
, to make it clearer that it's the same bitmask technique used elsewhere (as opposed to e.g. just keyed or indexed, as suggested by 'type')