1,097 karma · joined January 4, 2021
If you want to interact with their project, follow their rules on their terms, otherwise just grab the binaries and don't stir things up.
> (Mocking) Yes, that's why we should go back to Y with even worse static analysis.
Sure
Compare to [this](https://play.rust-lang.org/?version=stable&mode=debug&editio...)
There are separations to be made within autism, absolutely 100%, but the separations they hade made were also definitely 100% wrong.
I thought the builtins were defined in core and reexported by the prelude (they are defined in core, they're just implicitly in scope anyway).
But I still think expected behaviour is that builtins should have the same precedence as the prelude.
But on the other hand, it could be a bug as the trait resolver is commonly mentioned as the buggiest part of the language. I'm scared of the breakage if they fix it though.
All of these options require you to go out of your way to enable breakage.
You could also be in the super unlucky state of using something that was later proved unsound in std, which is the only case where rust will break your code on stable. (Missused unsafe in std)
If what you really mean is that you don't follow EU level politics, just say so.