-
Notifications
You must be signed in to change notification settings - Fork 13k
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 condition tutorial from doc index #12549
Comments
Sounds like #12539, but maybe we could repurpose this issue as to write a new one? |
Why would you want to write a new condition tutorial if there aren't conditions? |
The original condition guide actually covered four separate topics on handling errors/exceptions ("or other rare events"), not just conditions:
I suspect that once Conditions were gone, @alexcrichton figured there was little point in keeping the guide, though I suspect there might be some value in documenting the distinction between handling errors via Result-chaining versus Failure. |
The recent PR #13499 is relevant, someone suggested putting parts of it in an error handling tutorial. We should settle on whether we want a tutorial to deal with this or if we want to defer to rustdoc docblocks. |
I would like an error handling guide.
|
This has been completed, can someone close? |
Horray! |
…Veykril feat: Go to implementation of trait methods try goto where the trait method implies, rust-lang#4558
…atting-false-positive-when-commented-else, r=Alexendoo fix: `suspicious_else_formatting` false positive when else is included … This PR addresses an issue where invalid suggestions are generated for `if-else` formatting if comments contain the keyword `else`. The root of the problem is identified [here](https://github.com/rust-lang/rust-clippy/blob/95c62ffae9bbce793f68a6f1473e3fc24af19bdd/clippy_lints/src/formatting.rs#L217). Specifically, when a comment contains the word `else`, the lint mistakenly interprets it as part of an `if-else` clause. This misinterpretation leads to an incorrect splitting of the snippet, resulting in erroneous suggestions. fixes: rust-lang#12497 changelog: [`suspicious_else_formatting`]: Fixes invalid suggestions when comments include word else
This tutorial no longer exists.
The text was updated successfully, but these errors were encountered: