Stream: SIG-Guest-Languages

Topic: New C#/.net Subgroup

Timmy Silesmo (Sep 20 2023 at 17:58):

Hello everyone,
Yesterday a new subgroup for C#/.net was voted for and we are in the process of starting the new group. If this is something you would be interested in and would like to attend the meetings then please share your availability by following this link (NOTE: Times are in UTC+2): https://www.when2meet.com/?21455130-KHnGM

Scott Waye (Sep 26 2023 at 19:28):

https://github.com/yowl/WitCSharp I created README with the main issues we discussed at the meeting today. I just put it in a new repo, but please suggest a better place as required. It might be a basis for the next meeting to see which direction we want to take on the big ticket items. Feel free to request access to edit it.

Robin Brown (Sep 26 2023 at 19:59):

For language-ecosystem specific projects (e.g. bindgen, devtools) I personally think it'd be great for those to eventually belong to those ecosystems directly. Like .net dev tooling eventually ending up in the dotnet org someday. Tools that are still too early for that kind of integration/adoption or whose ecosystems don't have a single central place (e.g. componentize-py and compoenntize-js) have typically lived in the BA org itself.

Scott Waye (Sep 26 2023 at 20:55):

Ok, I have asked in the runtime group if they would like it there.

Till Schneidereit (Sep 27 2023 at 10:17):

[not with my TSC delegate hat on, since we don't have an established principle for this] fwiw I think that we should also be open to hosting these kinds of things indefinitely if there isn't a better place. For both componentize-js and -py I'm not sure where better they should live than in the BA org, and I think for the foreseeable future their development will very much be driven by BA contributors, so hosting them makes sense.

IMO the same approach makes sense for the C#/.Net bindings: if there is an obvious better place and interest by the language community to host it there, that makes sense. Otherwise I'd be happy to champion hosting in the BA org if you're interested

Michael Ball (Sep 27 2023 at 15:01):

Sorry, would have like to attend this meeting, where can I watch for the next?

Scott Waye (Sep 27 2023 at 15:21):

Till Schneidereit said:

[not with my TSC delegate hat on, since we don't have an established principle for this] fwiw I think that we should also be open to hosting these kinds of things indefinitely if there isn't a better place. For both componentize-js and -py I'm not sure where better they should live than in the BA org, and I think for the foreseeable future their development will very much be driven by BA contributors, so hosting them makes sense.

IMO the same approach makes sense for the C#/.Net bindings: if there is an obvious better place and interest by the language community to host it there, that makes sense. Otherwise I'd be happy to champion hosting in the BA org if you're interested

Thanks, just posted the question https://github.com/dotnet/runtimelab/issues/2409 in case the runtime people have an opinion.

Robin Brown (Sep 27 2023 at 17:50):

@Till Schneidereit I agree that we should be open to hosting them indefinitely as well. My response was meant to hint that there are two main reasons for the BA to host one of these projects now and potentially indefinitely:

1. If there isn't any singular place it makes sense to live, like in the case of the JS ecosystem for Componentize-JS
2. If there are some potential places it could be donated to but that's not fully clear or ready to happen yet, like in the case of Python for Componentize-Py

Robin Brown (Sep 27 2023 at 17:51):

Either way, some care should be taken in deciding where projects should be created and how that affects their development and governance.

Scott Waye (Oct 05 2023 at 18:22):

https://github.com/dotnet/runtimelab/issues/2409 is where we are currently discussing codegen if anyone wants to join in.

James Sturtevant (Oct 07 2023 at 00:10):

Thanks! I chimed in. Also thanks for the notes at https://github.com/yowl/WitCSharp, I think you captured the trade offs well.

James Sturtevant (Oct 07 2023 at 00:11):

Where is the rust implementation for the c# wit-bindgen? I couldn't find it

Scott Waye (Oct 09 2023 at 19:56):

James Sturtevant said:

Thanks! I chimed in. Also thanks for the notes at https://github.com/yowl/WitCSharp, I think you captured the trade offs well.

@Timmy Silesmo Can you give James access to the repo?

James Sturtevant (Nov 04 2023 at 17:22):

How do I run the test in https://github.com/bytecodealliance/wit-bindgen/blob/main/crates/csharp/tests/codegen.rs?

I ran cargo test -p wit-bindgen-cli --no-default-features -F csharp but that seems to on run the tests in tests/runtime?

Mossaka (Joe) (Nov 06 2023 at 09:40):

@James Sturtevant can you try cargo test -p wit-bindgen-csharp

James Sturtevant (Nov 21 2023 at 22:18):

@Timmy Silesmo guess you gave it the nudge it needed :tada: https://github.com/dotnet/runtime/issues/86985 merged!

James Sturtevant (Dec 04 2023 at 20:10):

check this out https://github.com/SteveSandersonMS/wasm-component-sdk

James Sturtevant (Dec 16 2023 at 01:23):

@Scott Waye @Timmy Silesmo I am not sure I will make it to the next meeting on Tuesday. My update:

• fixed bug in wasmtime::component for multiple exports: https://github.com/bytecodealliance/wasmtime/pull/7656
• added runtime tests for multiple exports: https://github.com/bytecodealliance/wit-bindgen/pull/787
• Started on Option type but found needed other things to pass the codegen tests for options like multi-return, and some basic variant support so started to add multi-return https://github.com/bytecodealliance/wit-bindgen/pull/794

Last updated: Dec 23 2024 at 12:05 UTC