Taiki Endo

The current one has the same behavior as [rand's `random`](https://docs.rs/rand/0.8.4/rand/fn.random.html#provided-implementations). However, I don't think there is any reason why `{f32,f64}_range` is not available, so I would accept a PR to...

This should be possible to do after adding a function similar to https://github.com/crossbeam-rs/crossbeam/commit/bd75c3c45edb78a731956c01458b75e5b69a8146 to [concurrent-queue](https://github.com/smol-rs/concurrent-queue).

Sorry for the breakage! As for this topic, I tend to follow rand's docs. > Any “value-breaking” changes to the generator should require bumping at least the minor version and...

This seems reasonable to me. ~~Probably, we can implement this by adding a CLI option to disable -show-instantiations in the following code.~~

> Probably, we can implement this by adding a CLI option to disable -show-instantiations in the following code. Hmm, I'm not sure how this can be implemented on our side...

Could you provide an example to reproduce this? Also, old results will be removed unless you pass `--no-report` to `cargo llvm-cov run`. ``` cargo llvm-cov run --no-report -- a cargo...

> * `--no-report` before `run` is silently ignored and This is https://github.com/taiki-e/cargo-llvm-cov/issues/151, and will be fixed by https://github.com/taiki-e/cargo-llvm-cov/pull/197 > * `--no-report` affects whether a rebuild happens [readme example](https://github.com/taiki-e/cargo-llvm-cov#merge-coverages-generated-under-different-test-conditions) describes `cargo...

> I've already figured out how to do / not do a rebuild, but it's still unexpected for a new user that adding --no-report will also change the build behaviour...

Added --no-clean flag as a workaround for this. See #214 for more.

In fact, there is already a way to do equivalent thing. The purpose of this problem is to make it easier to use that pattern. ```sh cargo llvm-cov --html #...