| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-03-23 | Refine error spans for const args in hir typeck | Michael Goulet | -4/+4 | |
| 2023-03-23 | Rollup merge of #109380 - Randl:patch-1, r=oli-obk | Matthias Krüger | -0/+52 | |
| add `known-bug` test for unsoundness issue Test for https://github.com/rust-lang/rust/issues/97156 | ||||
| 2023-03-20 | Add `known-bug` test for typeid unsoundness issue | Evgenii Zheltonozhskii | -0/+52 | |
| 2023-03-19 | Only expect a GAT const arg | Michael Goulet | -0/+29 | |
| 2023-02-23 | diagnostics: remove inconsistent English article "this" from E0107 | Michael Howell | -5/+5 | |
| Consider `tests/ui/const-generics/generic_const_exprs/issue-102768.stderr`, the error message where it gives additional notes about where the associated type is defined, and how the dead code lint doesn't have an article, like in `tests/ui/lint/dead-code/issue-85255.stderr`. They don't have articles, so it seems unnecessary to have one here. | ||||
| 2023-02-22 | diagnostics: update test cases to refer to assoc fn with `self` as method | Michael Howell | -1/+1 | |
| 2023-02-21 | Specify what 'this' actually is | Michael Goulet | -3/+3 | |
| 2023-02-11 | make `relate`'s const ty assertion use semantic equality | Boxy | -0/+181 | |
| 2023-02-05 | emit `ConstEquate` in `TypeRelating<D>` | Boxy | -0/+70 | |
| 2023-01-31 | Auto merge of #106399 - estebank:type-err-span-label, r=nagisa | bors | -1/+1 | |
| Modify primary span label for E0308 Looking at the reactions to https://hachyderm.io/`@ekuber/109622160673605438,` a lot of people seem to have trouble understanding the current output, where the primary span label on type errors talks about the specific types that diverged, but these can be deeply nested type parameters. Because of that we could see "expected i32, found u32" in the label while the note said "expected Vec<i32>, found Vec<u32>". This understandably confuses people. I believe that once people learn to read these errors it starts to make more sense, but this PR changes the output to be more in line with what people might expect, without sacrificing terseness. Fix #68220. | ||||
| 2023-01-30 | Modify primary span label for E0308 | Esteban Küber | -1/+1 | |
| The previous output was unintuitive to users. | ||||
| 2023-01-30 | Use ObligationCtxt::new_in_snapshot in satisfied_from_param_env | Michael Goulet | -0/+39 | |
| 2023-01-18 | i am free | Boxy | -2/+2 | |
| 2023-01-18 | actually print out non local anon consts | Boxy | -2/+2 | |
| 2023-01-18 | test for non local anon const printing | Boxy | -0/+36 | |
| 2023-01-18 | defer array len printing to const arg printing | Boxy | -4/+4 | |
| 2023-01-16 | Properly pluralize 'generic constants' | Michael Goulet | -7/+7 | |
| 2023-01-16 | ConstBlocks are poly if their substs are poly | Michael Goulet | -0/+31 | |
| 2023-01-12 | Rollup merge of #106702 - estebank:trait-bounds, r=compiler-errors | Matthias Krüger | -4/+19 | |
| Conserve cause of `ImplDerivedObligation` in E0599 CC #86377. | ||||
| 2023-01-12 | Rollup merge of #106309 - compiler-errors:prefer-non-err-candidates, r=oli-obk | Matthias Krüger | -42/+3 | |
| Prefer non-`[type error]` candidates during selection Fixes #102130 Fixes #106351 r? types note: Alternatively we could filter out error where-clauses during param-env construction? But we still need to filter out impls with errors during `match_impl`, I think. | ||||
| 2023-01-11 | Filter impl and where-clause candidates that reference errors | Michael Goulet | -42/+3 | |
| 2023-01-11 | Note predicate span on ImplDerivedObligation | Michael Goulet | -4/+6 | |
| 2023-01-11 | Conserve cause of `ImplDerivedObligation` in E0599 | Esteban Küber | -4/+19 | |
| CC #86377. | ||||
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+3267 | |
