frameworks not supported error about rust HOT 6 CLOSED

Removing those flags gets things working!

RUSTFLAGS="" wasm-pack build --target web --release
...
[INFO]: ✨   Done in 40.55s
[INFO]: 📦   Your wasm pkg is ready to publish at /Users/tom/workspace/dnssec-prover/wasmpack/pkg.

Thank you!

from rust.

https://github.com/cachix/devenv/blob/800f19d1b999f89464fd8e0226abf4b3b444b0fa/src/modules/languages/rust.nix#L124

Your nix configuration is passing a framework to a wasm build job.

The behavior of the wasm linker is to panic because it doesn't have anything useful it can do when told to link a framework.

from rust.

This behavior should be fixed to emit proper diagnostics, obviously, instead of an ICE. Diagnostics, possibly, that say what I just said.

from rust.

Excellent, thank you for confirming that!

from rust.

It's tempting to say we should just ignore the framework path for the wasm linker? But in my experience, even very senior software developers sometimes expect wasm to have some... truly magical powers. So I think explicitly rejecting it with an improved diagnostic is better. This helps more in the event of

• a programmer seriously expected that to work
• ...wasm somehow does grow magic powers and we can accept that?!?!

If people complain we can simply go to the ignoring path.

from rust.

I found out this is actually a duplicate of #122333

Neat!

from rust.