World

Every store, not the ones it is known to be in: a world keeps no per-entity list of its components, because that list is a second description of what the stores already know and it would be the thing that goes stale. The sweep is one remove per registered type, which is a number of component types rather than of entities.

The order is the store's: insertion, modified by swap-removal, so it is a walk and not an identity, and an index held across a removal names a different entity.

Unenforced, and that is not an oversight: a world outside a system has no declarations to enforce against. Inside one, go through SystemView.view, which checks first — see the note there for what happens if anything routes around it.

The cursor is borrowed and is given back when the loop ends — including when it breaks, which for…of reports through the iterator's return. A caller that keeps the result past its loop gets whatever the next query writes into it; see query.ts.

Every store, and the slot keeps one for each. A store is never removed from a world, so a later restore always finds the stores this save described still present — which is why nothing here has to record a component type, only its id.

A store the slot does not mention is emptied rather than skipped. Such a store was created after the save — by a query, or by something adding a component the world had never seen — and leaving its contents alone would leave components attached to entities the restored allocator says do not exist. Emptying it is what the snapshot actually claims.

The cursor pool is untouched: a borrowed cursor belongs to a loop that is running, and a rewind happens between ticks.