Giacomo Stevanato

That trait is unstable, so even if the contract could be followed, the trait itself can't be implemented

I would add using `rayon` to the suggestions since it's made pretty much for this usecase

> Generics interface: @thomcc brought up the possibility of using ArrayVec with deref traits to allow for some code reuse, see https://github.com/rust-lang/rfcs/pull/2990#issuecomment-848962572. I personally think that the interface has some...

Same problem here. log: http://hastebin.com/yegifuyoso.log Firefox 50.0b7 Windows 10 PassFF 0.1.32

> X.py has to be able to build with the beta compiler, so nightly should be never be required. However to do that it uses a freshly compiled stdlib. This...

`&Entities` is already a valid `SystemParam` which you can use to `.get(entity)` the entity's metadata, including its `ArchetypeId`. Given an `ArchetypeId` you can get the archetype's data using an `&Archetypes`,...

The migration guide could be changed to mention what needs to be adapter for the new changes, rather than the new changes themself. For example: > ## Migration guide >...

Note that this would make those derives incompatible with each other, as they would generate multiple `Reflect` `impl`s. I've seen some people derive both `Component` and `Resource` for a given...

Returning an actual `&mut World` would be unsound even with any form of entity disabling, as it still allows you to do structural changes that might affect the disabled entity....

Mhm that didn't happen when I ran `cargo run -p ci` on my Windows machine... Anyway, look like the error occurs because a `Component` wants to be only partially deserialized...