You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hashbrown into-iterators currently don't support Clone (see: rust-lang/hashbrown#545) but this shouldn't stop this crate from implementing it for its into-iterators, which ditch the hash table and just use vec::IntoIter internally.
The text was updated successfully, but these errors were encountered:
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 vec::IntoIter. We could possibly use Default for the wasted part instead, but that seems even weirder as a constraint. What do you think?
Hmm, that's actually an interesting point. It'd require unsafe code, but perhaps we could transmute to make the unused parts MaybeUninit, since we're just going to ignore their values anyway, and then set them to uninit?
The hashbrown into-iterators currently don't support
Clone
(see: rust-lang/hashbrown#545) but this shouldn't stop this crate from implementing it for its into-iterators, which ditch the hash table and just usevec::IntoIter
internally.The text was updated successfully, but these errors were encountered: