4 ms·
I think it could be an edition thing though... just say Rust 2019 will not allow `Command::before_exec`. By turning on edition 2019 you've accepted the new brak
by nixpulvis 8y ago
I think it could be an edition thing though... just say Rust 2019 will not allow `Command::before_exec`. By turning on edition 2019 you've accepted the new brakages that it imposes on you, and this is one of them.
Never mind the fact that the function is still a symbol in the STD library.
I understand if this is too much complier magic, though it seems like the correct idea to me anyway.
Am I missing something?
P.S. symbol version pinning seems like a great idea, I've even dreamt of having exposed syntax for it, e.g. `Foo::<i32>::bar@v1.3.2(arg1, arg2)`.
- steveklabnik 8y agoPlease see the discussion below; I already discussed this at length :)
- nixpulvis 8y agoJust so I'm clear, are you saying then that it's not possible or desireble to have Rust 201X code link against Rust 201Y STD? Or would that work? Sorry if I'm not making my thought very clear.
- steveklabnik 8y agoIt is not possible to have the standard library be different for different editions; it must be the same in all of them. There’s no #[cfg(edition=“”)] construct.
- nixpulvis 8y agoGotcha, thanks for taking the time to explain. I hope I didn't come off as being to negative about the change. Warnings are still a pretty good solution here.
- steveklabnik 8y agoIt’s all good!
- hyperman1 8y agoCan't there be a # [deprecate(untiledition=2018)] to solve this? The standard library contains all the old stuff but it becomes inaccessible in all editions after 2018.
- steveklabnik 8y agoThere can not.