Adam
Adam
I'd like to try if that's ok.
I guess its either: - adding some `TypeInfo::FixedSizeList` type (something like that) - use `TypeInfo::List` and override the `push` method to panic, and defining `insert` and `remove` to actually do...
name suggestions / general ideas: - `List` -> `DyanmicList` , `FixedLenList` -> `List` - "Collection" - "SizedList" - "DynamicArray" - "Slice" but I also think that `FixedSizeList` / `FixedLenList` are...
Rename many types to better reflect their usability (in the context of `Components` and `Resources`)
I'm not too attached to either. On one hand, using `ComponentId` and the like for resources is needlessly confusing (I remember I had had trouble with it) One the other...
looks like a segfault in `run-examples-macos-metal` ci? needs investigation e: fixed
> I'm not sure thee ZST separation is actually worth it. The cost of the branch is only needed up on `BlobVec::reserve_exact`, which is only called when the entities Vec...
I have no problem with going in this direction. But to play devil's advocate, I'll say that maybe if the only way to get a change-detection-enabled reference to a resource...
> Nice. What's the use case for fetching the same resource multiple times? I doubt there is a reasonable one. Should we restrict against it?
> Since the check for conflicting accesses doesn't depend on the world, we'd ideally perform it at compile time. Unfortunately [`const_type_id` isn't stable yet](https://github.com/rust-lang/rust/issues/77125), but we should revisit this when...
Thank you for your input, I implemented a lot of your suggestions. Now that `World::get_resource` is a "sub-set" of `World::get_resources` (you can call both `World::get_resource::()` and `World::get_resources::()` and get the...