Currently the way we generate "native" bindings is fairly strict and relevant to bevy.
I want this to be overhauled and runable on any crate importing bevy.
An ideal-case is being able to plug binding generation into a build.rs hook and generate bindings for all crates at lightning speed (think Rapier2D etc)
There is no way to avoid generating bindings short of bevy providing a function registration mechanism that can be re-used by us. The existing one requires boxing of all arguments which adds quite a bit of overhead (and doesn't let us plug into the argument conversion stages, which we heavilly rely-on)
Currently the way we generate "native" bindings is fairly strict and relevant to bevy.
I want this to be overhauled and runable on any crate importing bevy.
An ideal-case is being able to plug binding generation into a
build.rshook and generate bindings for all crates at lightning speed (thinkRapier2Detc)There is no way to avoid generating bindings short of bevy providing a function registration mechanism that can be re-used by us. The existing one requires boxing of all arguments which adds quite a bit of overhead (and doesn't let us plug into the argument conversion stages, which we heavilly rely-on)