Maayan Hanin

The plaintext output includes the `ErrorCode` (`NXDomain`, `ServerFailure` etc.), which the JSON output does not. Additionally, there are other response flags - which are not part of the JSON, such...

Feature Request: `iter_ones_from`

1

Currently, `iter_ones` and `iter_zeros` always begin from the first position (`front` is set to zero) and there is no easy way to begin iterating at a certain position. It would...

Fixes #272 The `i128` and `u128` experimental types are not well supported by emscripten, and `rand` doesn't support them when targeting emscripten. This PR excludes supports for `i128` and `u128`...

Fixes #274 Explicitly select `getrandom` with the `js` feature when building for `wasm32-unknown-unknown`

Compilation fails when building with `--target wasm32-unknown-unknown`. The reason is due to an indirect dependency: `quickcheck` depends on `rand` with the `getrandom` and `small_rng` features. However, `getrandom` only supports `wasm32-unknown-unknown`...

Tests fail for target wasm32-wasi

1

Running `cargo build --target wasm32-wasi` succeeds, but `cargo wasi test` fails: - The `pathbuf` fails since it relies on `env::temp_dir()`, which currently panics when running in wasi (see: https://github.com/WebAssembly/WASI/issues/306 )...

Add support for emscripten (wasm32-unknown-emscripten target)

3

I'm unable to build `quickcheck` when targeting the `wasm32-unknown-emscripten` build target. Please consider adding support for wasm as a 1st class citizen! Repro: Using `master` at `defde6fb0ce20b0c8c4e672aa9ae821f7d1f5b38`, Perform the following...

Clarify the rules of the Sushi Bar problem

1

The sushi bar problem description doesn't clarify all the rules that the solution must comply with. The rules can be inferred from the solutions, but they should be stated in...