wit-bindgen

wit-bindgen copied to clipboard

rust: accept fallible futures in `async_support::spawn`

10

Currently, `async_support::spawn` accepts an `impl Future`, but it should probably take something like `impl Future` instead, since the most common cases for spawned `Future`s involve fallible I/O, and forcing the...

dicej

c#: CI is extremely slow

9

Since C# CI was introduced it's been quite slow, but I realize that I haven't opened an issue about this. CI for C#, specifically on Windows, takes 30+ minutes whereas...

alexcrichton

Scala.js binding generator

10

Resolves https://github.com/bytecodealliance/wit-bindgen/issues/1159 I've only enabled the tests for linux, because on the macos runner it was extremely slow and on windows the `setup-scala` action does not seem to properly setup...

vigoo

> > Could you suggest another approach? WASI exports require WASI SDK and c-lang compilation anyway. We could also generate C code instead, just for this particular export type. And...

jsturtevant

> Final nit, why we are doing the BitConverter.ToInt32 dance ? this is coming from one of the other instructions that are generated via the wit-bindgen abi (https://github.com/bytecodealliance/wit-bindgen/blob/5d8fa6196b6382a90592c42aa63ad73f17760797/crates/csharp/src/function.rs#L400-L407) Maybe we...

jsturtevant

Scala.js binding generator

1

I have implemented a Scala.js binding generator in my fork (https://github.com/vigoo/wit-bindgen-scalajs/pull/1) which genreates Scala code that, when compiled with Scala.js, produces JS code compatible with jco/componentize.js Is this something that...

vigoo

C: handling of `@deprecated` items results in breaking changes

5

In https://github.com/WebAssembly/wasi-http/issues/133 @brendanburns reported that upgrading from `wasi/[email protected]` to `wasi/[email protected]` resulted in breaking changes in `wit-bindgen`'s C output, causing the following error: ```html /usr/local/lib/wasi-sdk-22.0/bin/clang -c wasi_http.c -o wasi_http.o wasi_http.c:48:5: error:...

yoshuawuyts

yowl

c#: perfer using fixed over GCalloc

1

see: - https://github.com/bytecodealliance/wit-bindgen/pull/1138#issuecomment-2624776578 - https://github.com/bytecodealliance/wit-bindgen/pull/1145#discussion_r1936315005 - https://github.com/bytecodealliance/wit-bindgen/pull/1138#issuecomment-2624961668 - https://github.com/bytecodealliance/wit-bindgen/pull/1138#issuecomment-2624776578

jsturtevant

c#: Update the allocation clean up code to avoid using closure which will allocate on the heap

1

> Also note that cleanups.Add(()=> NativeMemory.AlignedFree({address})); will allocate closure. > > Agree. I would consider handling this in a stack allocated `struct` that implements `IDisposable` or a `ref struct` with...

jsturtevant