.NET WebAssembly 샘플 수집

dimohy · 6월 28, 2024, 3:51오전

.NET(C#)으로 만들어진 웹어셈블리 샘플을 수집하고자 합니다.

dimohy · 6월 28, 2024, 3:52오전

샘플
https://ashleighadams.github.io/dotnet-webgl-sample/

dimohy · 7월 4, 2024, 6:22오전

C# + Blazor + WebAssembly + OpenGL = ?

https://github.com/dotnet/Silk.NET/tree/feature/wasm-take-4/src/Lab/Experiments/TriangleWasm
소스는 링크 깨짐

샘플
https://silkblazordemo.perksey.com/

rkttu · 7월 6, 2024, 10:27오전

닷넷을 WASM으로 빌드해서 WASI를 통해 실행되는 구현체들은 아직 뚜렷하게 드러난 것들은 보이지 않는 것 같고, 지금으로서는 Blazor가 대표적인 것 같습니다.

그리고 WASM이 어느정도 성숙해짐에 따라서, WASM 안에서도 가비지 컬렉터를 구현해보자는 움직임도 보입니다.

닷넷에서도 WasmGC를 도입해줄 수 있냐는 이야기도 진즉부터 논의는 된 것 같지만 구현이 달라서 쉽지는 않으나 계속 트라이 중이라는 이야기도 보이네요 ㅎㅎ

github.com/WebAssembly/gc

.NET Notes

opened 07:42AM - 11 Feb 20 UTC

vargaz

usage notes

I was asked to add some notes based on the needs of Microsoft .NET implementatio…ns wrt GC in WebAssembly. 1. Object layout .NET objects in memory usually consist of a header followed by object data. The header contains data such as: - the vtable/type pointer - a sync word for locking on the object - a length field for arrays/strings - for multi-dimensional arrays, a pointer to a struct describing the dimensions. The type system of the current proposal doesn't seem to be able to support this layout, i.e. a header followed by array data. Also, .NET supports arrays of structs, i.e. an array of {ref,non-ref} would look like in memory: [ref, non-ref, ref, non-ref, etc.]. In general, it seems very difficult to model all possible object layouts used by GCd languages. 2. Interior pointers In .NET, its quite common to have pointers into the middle of objects (arrays), and pointers to one past the end of an array. `anyref` doesn't seem to be able to support this. 3. Interop with C/C++ code The .net runtimes are written in C/C++ and assume that object references are normal C pointers which point to linear memory, and objects can be accessed from C code as a pointers to C structs. The current proposal places allocated objects outside linear memory and adds new accessors to read/write their contents. To allow manipulation of these objects from C code would require extensions to the C compilers. 4. Finalization The .net runtime needs to be notified somehow when an object with a finalizer dies. 5. Weak references .net supports multiple kinds of weak references which might not be supported by the underlying JS GC. 6. Non web runtimes Non-web runtimes would need to add a GC implementation, since GC is such a core feature that it probably cannot be treated as an optional feature like SIMD. 7. LLVM support The new types/type constructs don't exist in LLVM, not clear how they can be added.

dimohy · 8월 7, 2024, 3:27오전

Avalonia Webassembly 샘플

https://play.avaloniaui.net/

데모: Semi.Avalonia.Demo.Web

데모: Ursa.Demo.Browser

dimohy · 8월 20, 2024, 1:32오전

Avalonia Webassembly 샘플 - Solitaire

https://solitaire.xaml.live/