-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
rustc on error always prints the same two "task failed" lines #10036
Comments
This is actually a general problem in that when a task fails it will forcibly log the error to the task's logger. With #9967 coming down the pipe soon, I believe that the way forward with this is to have the message get propagated to the parent who then decides what to do with it. For rustc specifically, all of the monitored tasks wouldn't print their failure, the parents would receive the failure and then just ignore it (or print the ICE message). |
I don't think this is an issue anymore. |
This change fixes rust-lang#10036, "Extract to function assist implements nonexistent trait methods". When we detect that the extraction is coming from within a trait impl, and that a `self` param will be necessary, we adjust which `SyntaxNode` to `insert_after`, and create a new empty `impl` block for the newly extracted function.
…ait-impl, r=jonas-schievink fix: Extract function from trait impl This change fixes rust-lang#10036, "Extract to function assist implements nonexistent trait methods". When we detect that the extraction is coming from within a trait impl, and that a `self` param will be necessary, we adjust which `SyntaxNode` to `insert_after`, and create a new empty `impl` block for the newly extracted function.
Add beta-nominated label to triagebot Also non-maintainers should be able to label PRs with `beta-nominated`. changelog: none
It's more messy than informative, isn't it?
This might go away when rustc stops unwinding and just aborts, but I wonder whether we oughtn't have some way to suppress those messages, since I imagine a lot of commandliney programs that use unwinding won't want to expose their internal task failures to the console, unless they're tearing down the entire runtime with linked failure.
The text was updated successfully, but these errors were encountered: