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.
Another change extracted from #17362. I realised while reviewing it that there's no reason a reaction should ever be
MAYBE_DIRTYif it has no dependencies. After a reaction with no dependencies first runs, it goes fromDIRTYtoCLEAN, and should never again be anything other thanCLEAN.The corollary is that we can simplify the code in
is_dirty, because we know thatreaction.depsis notnull. Except that right now we do erroneously mark some effectsMAYBE_DIRTY— legacy$:effects — so this PR fixes that too.I'm not including a changeset with this one, because it's not making any user-observable changes (those
MAYBE_DIRTYeffects will never actually re-run, they will just unnecessarily go through theis_dirtyprocess and be markedCLEAN) and falls under the #17362 umbrella. Self-merging once green to continue with that PR.