FYI https://github.com/dotnet/runtimelab/issues/2468 following the meeting this morning, created this issue to get feedback and hopefully stimulate some conversation. Feel free to correct or whatever if you think I've not quite grasped the problem succinctly.
Wasi and Wasm components are providing some "worlds" or interfaces over functionality such as HTTP (https://github.com/WebAssembly/wasi-http). From a user perspective, if you were targeting wasm-wa...
Description When building an application targeting wasm and wasi and exporting it a function using UnmanagedCallersOnly results in the incorrect wasm type to be exported in the built wasm binary. T...
Description Wasm modules built with mono incorrectly includes wasi imports that aren't used by the module. This causes tests to fail for https://github.com/bytecodealliance/wit-bindgen. @AaronRobin...
Description Adding the following <WasmBuildNative>false</WasmBuildNative> to a property group in csproj and then building a project results in a successful build but no wasm binary is produces. @Aa...
Description With native-aot-llvm we are able to link a component type file by adding <NativeLibrary Include=\"{world_name}_component_type.o\" /> to the csproj file. With mono this doesn't do anythi...
Description Currently mono requires a main function when building for wasi. This shouldn't be required. Related: #96419 @AaronRobinsonMSFT @lewing @yowl @jsturtevant Reproduction Steps Try to build...
Scott Waye (Dec 19 2023 at 17:13):