today trait impl conflicts informed me that `&mut T` implements Iterator<Item = T>
Show this thread
-
ok apparently these conflict too: impl<T> Input<T> for &mut Vec<T> impl<T, I> Input<T> for I where I: Iterator<Item = T> but Vec<T> does not impl Iterator?! it does implement IntoIterator though, is that it?
Show this thread
Yeah, this is an intentional design of coherence in Rust. You're not allowed to rely on the fact that a type *doesn't* impl some trait unless either the type or trait are local to your crate. Otherwise adding any impl would be a major breaking change.