Skip to content

WASM support #17

@newpavlov

Description

@newpavlov

Currently for wasm32-unknown-unknown target we have two features stdweb and wasm-bindgen. In future the following changes can happen:

Following those changes may cause getrandom build breakage for some users, e.g. even if we'll write stdweb = ["wasm-indgen"] in Cargo.toml it may break build for users of older stdweb versions. Thus I believe we should think about how those changes can be handled in future.

I see 3 options:

  • Publish v0.2 on each deprecation, it's the most conservative option, but will cause a great deal of churn, because we will have to do breaking releases for downstream rand crates.
  • State that both WASM features are experimental and not covered by backward compatibility promise.
  • Move both WASM back-ends to separate crates and tell WASM users to use solution from embedded source compatibility #4.

cc @koute @alexcrichton

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions