Esteban Küber
dab3d5bb28
Never say "Trait
is implemented for {type error}
"
...
When a trait bound error occurs, we look for alternative types that
would have made the bound succeed. For some reason `{type error}`
sometimes would appear as a type that would do so.
We now remove `{type error}` from the list in every case to avoid
nonsensical `note`s.
2024-03-01 02:12:47 +00:00
Oli Scherer
5f6390f947
Continue compilation after check_mod_type_wf errors
2024-02-14 11:00:30 +00:00
Oli Scherer
83738a9b1c
Stop bailing out from compilation just because there were incoherent traits
2024-02-05 10:17:31 +00:00
Oli Scherer
db7cd57091
Remove track_errors entirely
2024-01-23 15:23:22 +00:00
George-lewis
d56cdd48cb
Bless tests
...
Update tests
2024-01-13 12:46:58 -05:00
Michael Goulet
7e38b70cc0
Split note, fix const/static impl trait error
2024-01-07 18:00:03 +00:00
Oli Scherer
beaf46f7e5
Work around the fact that check_mod_type_wf
may spuriously return ErrorGuaranteed
, even if that error is only emitted by check_modwitem_types
2023-10-25 12:04:54 +00:00
Oli Scherer
fd9ef69adf
Avoid a track_errors
by bubbling up most errors from check_well_formed
2023-10-20 08:46:27 +00:00
Esteban Küber
041e54bd92
Tweak wording of E0562
...
Fix #80476 .
2023-10-04 19:51:43 +00:00
Michael Goulet
30e6cea0ae
Point out if a local trait has no implementations
2023-09-10 21:20:36 +00:00
Camille GILLOT
87233da5c2
Check entry type as part of item type checking.
2023-07-15 22:02:16 +00:00
Michael Goulet
b14eb0c497
pluralize stuff
2023-02-22 21:52:26 +00:00
Michael Goulet
3f80017f03
Better label for illegal impl trait types
2023-02-14 23:12:27 +00:00
Albert Larsan
cf2dff2b1e
Move /src/test to /tests
2023-01-11 09:32:08 +00:00