fix: always mark reactions of deriveds #16457
Merged
+98
−12
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.
This was absolute hell to isolate. Essentially: if a derived is read inside a time-travelling batch, it isn't (and can't) be marked clean afterwards, which means that if one of its dependencies later becomes dirty, reactions of the derived are not notified.
I was worried that this would impact performance, but surprisingly this appears to be faster:
I can only assume that having extra recursion in a tiny minority of cases is outweighed by having fewer bitwise operations in all other cases.
Before submitting the PR, please make sure you do the following
feat:
,fix:
,chore:
, ordocs:
.packages/svelte/src
, add a changeset (npx changeset
).Tests and linting
pnpm test
and lint the project withpnpm lint