Closed AThilenius closed 5 years ago
After more digging and a few forks later I've realized this issue is more complicated for the amethyst_core
case because it pulls in Rayon
directly. Both specs and specs-hierarchy have default-features = false
for shred
, so adding the same to amethyst_core
should take care of that part. Going to close this, but it might still be worth considering?
Rust thread support isn't there yet for WASM (as far as I understand) 😢
Normally this wouldn't be a problem because
shred
seems to work just fine with WASM as long as youdefault-features = false
in theCargo.toml
. Sadly this is not possible for me becausedefault-features
doesn't affect transitive deps and I'm using amethyst_core which is pulling inspecs
which pulls inshred
. (Aka because of a lot of RFCs and issues related to Cargo, I don't think I have a way to compileshred
withdefault-features = false
)Using the
DispatcherBuilder
causes a panic:backend.js:1 Panic error message: Invalid configuration: ThreadPoolBuildError { kind: IOError(Custom { kind: Other, error: "operation not supported on wasm yet" }) }
Should
parallel
be disabled by default forwasm32
? I'm not even sure how to add something like that to theCargo.toml
.