Josh Stone

One thing that's kind of weird is that `IntoKeys` will still need `V: Clone`, and `IntoValues` will need `K: Clone`, so we can have a complete clone of the underlying...

#348 is adding the easy ones for `IntoIter`, but we can leave this open for `IntoKeys` and `IntoValues`.

(Note that `hashbrown/borsh` is irrelevant to `dashmap` though, and probably most `hashbrown` users in general.)

It's unfortunately tied to the `PrimInt` trait, as mentioned in . For that reason, I think a "soft" deprecation is better so folks don't have to squash a warning they...

The actual error: ``` error[E0308]: mismatched types --> /home/jistone/.cargo/registry/src/index.crates.io-6f17d22bba15001f/num-bigint-0.4.0/src/biguint/convert.rs:70:19 | 70 | .div_ceil(&big_digit::BITS.into()) | -------- ^^^^^^^^^^^^^^^^^^^^^^^ expected `u64`, found `&_` | | | arguments to this method are incorrect |...

> because floats saturate at `±INF` I'm not sure I agree -- infinity is more like an overflow in my mind. The saturated integer values are still finite (of course),...

For some context, this was a pretty recent change in Rust for `Sum`: * https://github.com/rust-lang/rust/pull/129321 * https://users.rust-lang.org/t/why-is-the-additive-identity-of-floats-0-0/128016 I still have some mild misgivings about it: * Mathematically, zero has no...

> I think it's reasonable to say that those that want that property can initialize with `vec![0.0, len()]` directly. They can't do that for a generic `T: Zero` though, e.g....

Actually, let's ask -- @bluss @jturner314, how would you feel about this in `ndarray`'s case? (or in general)

`nalgebra` is similarly generic, @sebcrozet @milibopp what do you think?