From e84930266d077eea7671e93b73d8b0aec5b39bc7 Mon Sep 17 00:00:00 2001 From: pavelsavara Date: Wed, 18 Oct 2023 17:30:04 +0200 Subject: [PATCH] fix --- accepted/2023/wasm-browser-threads.md | 1 - 1 file changed, 1 deletion(-) diff --git a/accepted/2023/wasm-browser-threads.md b/accepted/2023/wasm-browser-threads.md index e06b4d091..bc03076fa 100644 --- a/accepted/2023/wasm-browser-threads.md +++ b/accepted/2023/wasm-browser-threads.md @@ -587,7 +587,6 @@ Move all managed user code out of UI/DOM thread, so that it becomes consistent w - This will also start in Blazor project, but UI rendering would not work. - we have pre-allocated pool of browser Web Workers which are mapped to pthread dynamically. - we can configure pthread to keep running after synchronous thread_main finished. That's necessary to run any async tasks involving JavaScript interop. - - GC is running on UI thread/worker. - legacy interop has problems with GC boundaries. - JSImport & JSExport work - There is private JSSynchronizationContext implementation which is too synchronous