A possible solution here would be to split proptest into two crates:

• a proptest-traits, which exposes strategy trait and related machinery. This part could be strictly pure & platform-independent I think?
• proptest-runner, which allows one to actually run property test, maintaining a failure database, etc.

EDIT: this would help because we depend on prop-test in a non-optional way to define an "Arbitrary" instance for text edits. It would be totally fine if the actual tests work on Linux/Windows/Mac.

I gated the code you deleted behind a cfg check in 0.9.2, so I think it should be working for you now.

split proptest into two crates

Unfortunately, the two are rather intertwined — even the basic public API requires Strategy to know about TestRunner and vice versa.

Were any of you able to get proptest to compile for WebAssembly? I am running into this error:

error[E0433]: failed to resolve: use of undeclared crate or module `imp`
  --> /home/lastmjs/.cargo/registry/src/github.com-1ecc6299db9ec823/wait-timeout-0.2.0/src/lib.rs:66:9
   |
66 |         imp::wait_timeout(self, dur)
   |         ^^^ use of undeclared crate or module `imp

I turned off all features except for std, and it now compiles.

Have you had success actually getting proptest to run? I keep getting a panic when trying to create a runner: Panicked at 'not supported on this platform', library/std/src/sys/wasm/../unsupported/os.rs:76:5

^ that's about how far I got too, with a more precise message in a few places:

panicked at 'condvar wait not supported', library/std/src/sys/wasm/../unsupported/locks/condvar.rs:23:9

🤦 Just saw #270

proptest! {
    #[wasm_bindgen_test]
    fn some_test(num: u32) { assert_eq!(num, num); }
}