Peter Jaszkowiak
Peter Jaszkowiak
Is my understanding that this would fulfill the `Math.random()` use case?
How can the array be "too big"? Don't `array_windows` and `array_chunks` always return a reference into already-allocated memory?
You could still use the array like you would a slice though, right?
In that case, why not provide a drop-in `HashMap` replacement which defaults to a deterministic hasher? Or why not provide a `RandomState` replacement which is deterministic?
I'm a little confused then. From your explanation of the `Mutex` / `rand` stuff it sounds like that's the normal approach. Does the same not apply to those?
Might want to edit the title into an appropriate summary of your request
Confirming this is still a problem on 14.0.3
@archief2910 see the discussion in the previous implementation pr: https://github.com/rust-lang/rust-clippy/pull/12914 Essentially, you may want to wait until we know more about the direction in rustc and std.
You also shouldn't claim an issue that's already assigned, without first attempting to contact the assignee.
Correct, #13770 is unrelated. I was confused earlier