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
We generally don't want to bind to things that can't be bound in JS, so we should check to see if these APIs were added in v112 and implement them when available.
It also seems like we need to implement an API for the "type builder" API in binaryen.
The text was updated successfully, but these errors were encountered:
Binaryen 111 added C APIs for most GC-related functions, such as:
WebAssembly/binaryen@version_110...version_111#diff-5d2db7a99567fbac5e617fd39709fbdca0a2d22b92a97d5c3515caf7dba9f78bR1035-R1154 and WebAssembly/binaryen@version_110...version_111#diff-5d2db7a99567fbac5e617fd39709fbdca0a2d22b92a97d5c3515caf7dba9f78bR2335-R2706
However, they left them all as TODO in the JS code (see WebAssembly/binaryen@version_110...version_111#diff-9f4ceff4b9bcc272e133f83651e487c15f772e6115c88023c2435cc5226d8b68R2438-R2448)
We generally don't want to bind to things that can't be bound in JS, so we should check to see if these APIs were added in v112 and implement them when available.
It also seems like we need to implement an API for the "type builder" API in binaryen.
The text was updated successfully, but these errors were encountered: