This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Differences with bevy_reflect #298
Comments
|
So I've been explicitly avoiding looking at their design thus far, to kind of keep a clean head. One difference I know on top of my head is that bevy_reflect has a "type registry", whereas facet has an associated const. Ideally, as const capabilities improve in Rust, it'll be possible to do all sorts of things in const fn contexts based on Facet's data structures. For now there are blockers (ConstTypeId shenanigans, PartialEq::eq in const, rescursive consts etc.) — but those are being discussed by various rust teams. I think in terms of performance there are different goals, too — but again, I feel like if I took a detailed look at bevy_reflect it would kind of anchor my expectations and it would make it harder to just think from first principles so I'm going to willingly avoid doing that, and I'd be grateful if folks can exercise patience and not list too many differences in this topic right now yet. |
|
Hey @fasterthanlime, Bevy's SME-Reflect here! I know you haven't looked at Since Bevy is a game engine, one thing we want to support as easily as possible is scripting and types fully defined at runtime (e.g. from a scripting language). We're not fully there yet, but that is one of our goals. Is this a similar goal for |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Bevy is a game engine written in Rust, and it has a reflection library: https://docs.rs/bevy_reflect/latest/bevy_reflect/
The text was updated successfully, but these errors were encountered: