You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its structure makes it hard to implement garbage collection vs finalization registry because we can’t differentiate JS refererence Vs native pointer
It bloats the binary/bundle and adds required runtime support. Goes in the opposite direction of being able to generate portable wasm targeting only WASI.
Our patching of its interface is hard to reason about or add to.
We should instead add the code for the object representation and have it call Yoga C APIs directly, like the JNI bindings.
The text was updated successfully, but these errors were encountered:
This isn’t something I’m going to prioritize, but might be worth picking up as a next step in evolving the bindings, especially if standalone wasm es modules become well supported.
embind is convenient but not ideal
We should instead add the code for the object representation and have it call Yoga C APIs directly, like the JNI bindings.
The text was updated successfully, but these errors were encountered: