mirror of
https://github.com/rust-lang/rust.git
synced 2025-05-14 02:49:40 +00:00
1f9fa2305a
We have several methods indicating the presence of errors, lint errors, and delayed bugs. I find it frustrating that it's very unclear which one you should use in any particular spot. This commit attempts to instill a basic principle of "use the least general one possible", because that reflects reality in practice -- `has_errors` is the least general one and has by far the most uses (esp. via `abort_if_errors`). Specifics: - Add some comments giving some usage guidelines. - Prefer `has_errors` to comparing `err_count` to zero. - Remove `has_errors_or_span_delayed_bugs` because it's a weird one: in the cases where we need to count delayed bugs, we should really be counting lint errors as well. - Rename `is_compilation_going_to_fail` as `has_errors_or_lint_errors_or_span_delayed_bugs`, for consistency with `has_errors` and `has_errors_or_lint_errors`. - Change a few other `has_errors_or_lint_errors` calls to `has_errors`, as per the "least general" principle. This didn't turn out to be as neat as I hoped when I started, but I think it's still an improvement. |
||
|---|---|---|
| .. | ||
| astconv | ||
| check | ||
| coherence | ||
| collect | ||
| impl_wf_check | ||
| outlives | ||
| structured_errors | ||
| variance | ||
| autoderef.rs | ||
| bounds.rs | ||
| check_unused.rs | ||
| collect.rs | ||
| constrained_generic_params.rs | ||
| errors.rs | ||
| hir_wf_check.rs | ||
| impl_wf_check.rs | ||
| lib.rs | ||
| structured_errors.rs | ||