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.
We prune effects that have no dependencies and no children. But in many cases we can be more aggressive — if we have an
{#if browser}
block, for example,browser
is never going to change and so it's useless to add the block effect to the effect tree, other than to indirectly add its children.Another example is an attachment that doesn't read anything reactive (i.e.
{@attach (node) => {...}}
, which is probably 99% of cases). Today, if you uselog_effect_tree
to look at the effect tree immediately after mounting this component......you see this:
After this PR, it looks like this — notice the intermediate
block
effects have been replaced by their children:This means less memory pressure (effects can be garbage collected), and faster traversal. Though admittedly it's hard to see a clear win in the benchmark results:
Results of `pnpm bench:compare`
I suspect this is a case where a benchmark fails to capture the reality of a large application.
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