4 ms·
What you're describing sounds more like a potential issue with editions if/when they allow breaking stdlib changes more than a problem with editions as they exi
by aw1621107 8mo ago
What you're describing sounds more like a potential issue with editions if/when they allow breaking stdlib changes more than a problem with editions as they exist today, which is more what I took the original comment to be talking about.
- pjmlp 8mo agoExactly because they don't allow it, they don't cover all scenarios regarding language evolution
- aw1621107 8mo agoOK, sure, but again what breaking changes editions do/don't currently allow is independent from what SkiFire13/I was responding to, which was the "requires full access to source code" bit.
- pjmlp 8mo agoHow do you expect a compiler to be able to mix and match changes across editions between crates, if those happen to be changes in semantic behaviour?
- aw1621107 8mo agoDepends on the change. Obviously the compiler doesn't need to care about cross-edition compatibility between crates if the changes in question don't impact the public API. Otherwise, I'd expect the compiler to canonicalize the changes, and from what I understand that is precisely how edition changes are chosen/designed/implemented.