feat: allow reading tag variables after they are written #2745
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.
Description
Tag variables staying in the past after being written has been shown to be cumbersome, error prone, and confusing.
With that we decided to allow reading the "proposed" value after a tag variable has been written.
It is considered "proposed" because rendering logic, derivations and change handlers do not run eagerly when the assignment happens, however in the scope of the current expression you are able to read the last assigned to value of the tag variable.
Checklist: