James Sturtevant

closing for now until calico has better support /close

@alexcrichton might be the best to give some insight here as to whether this is possible or if there are other constraints

Unfortunate that the powershell command doesn't work properly on Windows 2025. /lgtm /approve

I looked into using the generator. The generator takes the approach of doing low level bindings (https://github.com/dotnet/ClangSharp/issues/509#issuecomment-1846163712 and https://github.com/dotnet/ClangSharp/issues/427#issuecomment-1836370041). This requires a slightly different approach and use of unsafe in...

Interesting, I wasn't thinking of this use case (although the binding generator calls this out as one reason for this approach). We don't currently expose those bindings in a public...

Checking in on this request, what is the process for moving forward? Is there a meeting I can add this to an agenda? Thanks!

Thanks for the update and all makes sense! As additional information we found that the Zephyr project (Linux foundation) redistributes the library (https://docs.zephyrproject.org/latest/develop/languages/c/picolibc.html).

The mis-configuration came from using the macro in a way that was intended for testing purposes only (https://docs.rs/wit-bindgen/latest/wit_bindgen/macro.generate.html#options-to-generate) > // Usually used in testing, our test suite may want to...

I believe this is a simplified reproduction: https://github.com/jsturtevant/wasi-cli/tree/prev-is-none I am getting: ``` cargo build Compiling wit-bindgen-rust-macro v0.39.0 Compiling wit-bindgen v0.39.0 Compiling path-repo v0.1.0 (/home/jstur/projects/wit/wasi-cli) error: proc macro panicked --> src/main.rs:2:5...

Should we keep this open? I can rename it to reflect the error.