-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove DiagnosticBuilder.quiet #93229
Conversation
Like I said, please provide an alternative before removing this. |
Talked with @oli-obk and the simplest solution is to just fix errors reported by the compiler (some missing |
If it's an acceptable tradeoff, I would use the typical pattern of requesting It might even be easier to not engage in those name resolution / @bors r+ |
📌 Commit cf382de has been approved by |
@GuillaumeGomez my understanding is that this feature is causing soundness issues (because it turns errors off completely). From @eddyb's reaction when talking to me about it it seems like this very much should never have happened. As such I see zero reason why an experimental rustdoc feature should delay the fixing of such a bug. Like, I know the issue got resolved already, but I want to make sure our priorities are straight here. |
@Manishearth Perhaps you (like me) missed their most recent message? |
@mark-i-m No, I saw the updates (and there's a line in my comment acknowledging the issue got resolved already), from the rustdoc side I'm very strongly against bugs in this experimental feature blocking soundness fixes (or really, any compiler work) and want to push back against our team adopting such an attitude. |
I don't think what I asked was unreasonable. This has been around for months and it seems normal for me to worry about how to go around this limitation.
Humans make mistakes. Please scold me in private next time. There is nothing about "such an attitude", just a legitimate concern. |
To be fair, it's been around for months with |
As far as I know it's only used in rustdoc but I understand your problem with it. As for this, since it was in the error system, I thought that @estebank was the one responsible. Sorry for the noise. |
…askrgr Rollup of 8 pull requests Successful merges: - rust-lang#91526 (rustc_lint: Some early linting refactorings) - rust-lang#92555 (Implement RFC 3151: Scoped threads.) - rust-lang#93213 (Fix `let_chains` and `if_let_guard` feature flags) - rust-lang#93219 (Add preliminary support for inline assembly for msp430.) - rust-lang#93226 (Normalize field access types during borrowck) - rust-lang#93227 (Liberate late bound regions when collecting GAT substs in wfcheck) - rust-lang#93229 (Remove DiagnosticBuilder.quiet) - rust-lang#93234 (rustc_mir_itertools: Avoid needless `collect` with itertools) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
r? @eddyb
cc #69426 @GuillaumeGomez @Manishearth