Pauan

@Horcrux7 I don't see how that's relevant to this issue. This issue is about making browser-specific APIs optional so that way Wasm remains portable. And that's already true today: any...

> @redradist There are considering DOM API directly from Wasm to Browser without JavaScript glue code and my suggestion is for any such sub-API create the separate specification ... They...

@ndarilek That's a really good question. It's most convenient for the user to use Futures, but Futures are currently unstable in stdweb. I think the ideal would be to have...

@ndarilek APIs in wasm-bindgen are also added in individually, which is pretty much necessary due to Rust's restrictions (static types and memory model). Even their system to auto-generate bindings based...

@Boscop I'm not sure. I don't see any technical reason why it couldn't, but I doubt it does right now.

> users expect equality to be semantic equality, not memory pointer equality (identity). It is true that *most* things in Rust use semantic equality, but not everything: * [`NonNull`](https://doc.rust-lang.org/nightly/src/core/ptr.rs.html#3010-3015) *...

To really prove the point that equality isn't special, [here's the implementation of equality for slices](https://doc.rust-lang.org/nightly/src/core/slice/mod.rs.html#4862-4870) (including `Vec`): ```rust impl PartialEq for [A] where A: PartialEq { fn eq(&self, other:...

@captain-yossarian I don't have write permission, so only @koute can merge things.

I upgraded my `rustc` and now I'm getting this error too. ``` > rustup show Default host: x86_64-pc-windows-msvc installed toolchains -------------------- stable-x86_64-pc-windows-msvc nightly-x86_64-pc-windows-msvc (default) installed targets for active toolchain --------------------------------------...

Similar to https://github.com/koute/cargo-web/issues/121, if I build without `--release` then it works fine, so this bug only happens in `--release` mode.