microsoft / microsoft/rust-guidelines
M-ERRORS-CANONICAL-STRUCTS - Don't add `is_foo()` and similar if no one would act on these.
Open
issue
- Dominant language
- Rust
- Stars
- 200
- Forks
- 25
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
Errors should be as opaque as feasible, but not more or less.
Contributor guide
Research direction
Start by reading the repository's Rust guidelines and the issue's principle about opaque errors. No file, test, or entry point is named, and the issue does not define a concrete change or a clear completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100