61bd3af7c7
# Objective This is the first step of #19430 and is a follow up for #19132. Now that `ArchetypeRow` has a niche, we can use `Option` instead of needing `INVALID` everywhere. This was especially concerning since `INVALID` *really was valid!* Using options here made the code clearer and more data-driven. ## Solution Replace all uses of `INVALID` entity locations (and archetype/table rows) with `None`. ## Testing CI --------- Co-authored-by: Chris Russell <8494645+chescock@users.noreply.github.com> Co-authored-by: François Mockers <francois.mockers@vleue.com> Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com> |
||
|---|---|---|
| .. | ||
| clone_entities.rs | ||
| entity_set.rs | ||
| hash_map.rs | ||
| hash_set.rs | ||
| hash.rs | ||
| index_map.rs | ||
| index_set.rs | ||
| map_entities.rs | ||
| mod.rs | ||
| unique_array.rs | ||
| unique_slice.rs | ||
| unique_vec.rs | ||