3 ms·
This might be the wrong place to ask but does anyone know what’s the situation with fixing Range not implementing Copy? I ran into this the other day again and
by adamnemecek 5y ago
This might be the wrong place to ask but does anyone know what’s the situation with fixing Range not implementing Copy? I ran into this the other day again and way annoyed.
- steveklabnik 5y agohttps://github.com/rust-lang/rfcs/issues/2848#issuecomment-826352378 https://github.com/rust-lang/rfcs/issues/2848#issuecomment-8...
- adamnemecek 5y agoThanks, I wasn't sure if there was some other discussion that was not on Github.
- steveklabnik 5y agoIf there is I’m not aware of it, but that certainly doesn’t mean there isn’t; I wouldn’t be in the room if there was.
- deleted 5y ago[deleted]
- epage 5y agoLast update on the issue is from April 25th https://github.com/rust-lang/rfcs/issues/2848#issuecomment-826352378 https://github.com/rust-lang/rfcs/issues/2848#issuecomment-8...
- terhechte 5y agoNot sure why you were downvoted. I also wondered about that when I started with Rust. I'd love to see this at some point but I just started cloning ranges everywhere. As most of my ranges are simple (e.g. just a Range<usize>) the main downside I see is the additional clone calls.