Reflect everything by default & make it opt out about bevy

[SkiFire13]

Note that this would make those derives incompatible with each other, as they would generate multiple Reflect impls. I've seen some people derive both Component and Resource for a given type, so this might not be ideal.

As an alternative: is it strictly necessary for them to derive Reflect? Or could they just register something like ReflectComponent in the TypeRegistry, internally using some kind of remote reflect to sidestep not knowing whether Reflect is implemented or not?

[alice-i-cecile]

We could also add a real trait bound to all of these types. This would be more intrusive and limiting and worsen compile times, but would arguably be more idiomatic.

I think that implicitly doubling up on the derives is a better solution though.

[iiYese]

That sounds better