Description
In our current 2.0 Assimp bindings we only expose 1:1 native bindings which are generated by our BuildTools generator. This is good, however it isn't very user friendly as it involves a lot of usage of unsafe and other native paradigms that aren't easy for beginners (you can see an example of it being used here and it's not as pretty as it could be)
Similar to assimp.net, we'd like to expose a higher-level managed wrapper on top of our low-level bindings so that it's easier to use and easy for people who've never used Assimp before to pick up. This could be done in steps, for example in one PR laying out an API surface, and slowly implementing it in subsequent PRs.
If you have any further questions feel free to join our Discord server - we're pretty much always active there.