Aran Donohue
Aran Donohue
That would have saved me some confusing broken builds!
For any other readers, for reference, my full command is: ``` flutter_rust_bridge_codegen build-web --release --wasm-pack-rustflags "-C target-feature=+atomics,+bulk-memory,+mutable-globals --remap-path-prefix $HOME=/build" ```
I confirmed that if I convert my data structure that is involved in this from RustAutoOpaque to translatable, the issue no longer occurs (or maybe occurs much more rarely). When...
A couple other notes, without solving anything: * there is also `Atomics.waitAsync`, supported everywhere except Firefox, and my understanding is it can be supported in Firefox at lower performance with...
Repro: https://github.com/aran/frb-exc-repro/blob/mut/lib/main.dart
After some more thought, it's clearer now: When targeting wasm there is no safe way to use standard concurrency primitives that ultimately depend on `Atomics.wait`. In particular any frb(sync) function...
With no further changes to FRB, the simplest way to make Rust mutable data safe might be to choose either async or sync globally. Either run everything in the thread...
Apologies for the lack of clarity - in all of the above, when talking about async functions, I only meant non-`async` Rust functions that are not labeled `frb(sync)` and are...
Up to you how you want to track full solutions. For my case I am working around issues by exclusively using frb(sync) and I've turned on `full_dep` although I'm not...
https://github.com/aran/frb-exc-repro