summary refs log tree commit diff
path: root/src/test/ui/error-codes
AgeCommit message (Collapse)AuthorLines
2019-10-31Fix incorrect diagnostics for expected type in E0271 with an associated typeOhad Ravid-3/+3
2019-10-29Rollup merge of #65562 - Patryk27:master, r=estebankMazdak Farrokhzad-1/+1
Improve the "try using a variant of the expected type" hint. Fix https://github.com/rust-lang/rust/issues/65494. - Change type-printing output. - Use `span_to_snippet` when possible. - Change the message to `try using a variant of the expected enum`
2019-10-29Rollup merge of #65318 - estebank:coherence, r=varkorMazdak Farrokhzad-8/+12
Call out the types that are non local on E0117 CC #24745.
2019-10-28Improve the "try using a variant of the expected type" hint.Patryk Wychowaniec-1/+1
2019-10-28Do not display ADT type arguments and fix rebaseEsteban Küber-1/+1
2019-10-28Account for tuples in explanationEsteban Küber-1/+1
2019-10-28Talk about specific types and remove lifetimes from outputEsteban Küber-1/+1
2019-10-28Use more targeted spans for orphan rule errorsEsteban Küber-8/+12
2019-10-28Call out the types that are non local on E0117Esteban Küber-2/+2
2019-10-27Point at local similarly named element and tweak references to variantsEsteban Küber-13/+19
Point at the span for the definition of ADTs internal to the current crate. Look at the leading char of the ident to determine whether we're expecting a likely fn or any of a fn, a tuple struct or a tuple variant. Turn fn `add_typo_suggestion` into a `Resolver` method.
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+9
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-17Point at enclosing function without `self` receiverEsteban Küber-4/+10
2019-10-17Refer to "associated functions" instead of "static methods"Esteban Küber-1/+1
2019-10-14Rollup merge of #65398 - estebank:capitalization-only, r=varkorTyler Mandry-1/+1
Bring attention to suggestions when the only difference is capitalization CC #65386.
2019-10-14Rollup merge of #65292 - JohnTitor:add-backticks, r=varkor,CentrilMazdak Farrokhzad-2/+2
Print lifetimes with backticks Fixes #65287 r? @varkor
2019-10-13Bring attention to suggestions when the only difference is capitalizationEsteban Küber-1/+1
2019-10-13Rollup merge of #65248 - estebank:mention-if-let, r=cramertjMazdak Farrokhzad-0/+7
Suggest `if let` on `let` refutable binding Fix #58385.
2019-10-11Print lifetimes with backticksYuki Okushi-2/+2
2019-10-09Suggest `if let` on `let` refutable bindingEsteban Küber-0/+7
2019-10-07update ui testsGuillaume Gomez-0/+1
2019-10-03typo: fix typo in E0392Ben Boeckel-1/+1
See #64931.
2019-10-03Rollup merge of #64931 - estebank:missing-param-ref, r=matthewjasper,CentrilMazdak Farrokhzad-1/+1
Reword E0392 slightly Make it clearer that a type or lifetime argument not being used can be fixed by referencing it in a struct's fields, not just using `PhathomData`. CC #53589.
2019-10-02review commentEsteban Küber-1/+1
2019-09-30Reword E0392 slightlyEsteban Küber-1/+1
Make it clearer that a type or lifetime argument not being used can be fixed by referencing it in a struct's fields, not just using `PhathomData`.
2019-09-29Rollup merge of #64691 - estebank:unexpected-variant, r=CentrilMazdak Farrokhzad-0/+3
Point at definition when misusing ADT When given `struct Foo(usize)` and using it as `Foo {}` or `Foo`, point at `Foo`'s definition in the error.
2019-09-29Rollup merge of #63492 - eddyb:cvarargs, r=nagisa,matthewjasperMazdak Farrokhzad-14/+12
Remove redundancy from the implementation of C variadics. This cleanup was first described in https://github.com/rust-lang/rust/issues/44930#issuecomment-497163539: * AST doesn't track `c_variadic: bool` anymore, relying solely on a trailing `CVarArgs` type in fn signatures * HIR doesn't have a `CVarArgs` anymore, relying solely on `c_variadic: bool` * same for `ty::FnSig` (see tests for diagnostics improvements from that) * `{hir,mir}::Body` have one extra argument than the signature when `c_variadic == true` * `rustc_typeck` and `rustc_mir::{build,borrowck}` need to give that argument the right type (which no longer uses a lifetime parameter, but a function-internal scope) * `rustc_target::abi::call` doesn't need special hacks anymore (since it never sees the `VaListImpl` now, it's all inside the body) r? @nagisa / @rkruppe cc @dlrobertson @oli-obk
2019-09-28rustc: rely on c_variadic == true instead of CVarArgs in HIR/Ty fn signatures.Eduard-Mihai Burtescu-14/+12
2019-09-27getting more context for duplicate lang items (fixes #60561)Tomas Tauber-1/+1
Where possible, the error message includes the name of the crate that brought in the crate with duplicate lang items (which helps with debugging). This information is passed on from cstore using the `extern_crate` query.
2019-09-25Rollup merge of #64746 - estebank:elide-impl-trait-obligations-on-err, ↵Mazdak Farrokhzad-6/+20
r=cramertj Remove blanket silencing of "type annotation needed" errors Remove blanket check for existence of other errors before emitting "type annotation needed" errors, and add some eager checks to avoid adding obligations when they refer to types that reference `[type error]` in order to reduce unneeded errors. Fix #64084.
2019-09-24Fix #64744 -- handle zero sub-pats case.Mazdak Farrokhzad-2/+16
2019-09-24Remove blanket silencing of "type annotation needed" errorsEsteban Küber-6/+20
Remove blanket check for existence of other errors before emitting "type annotation needed" errors, and add some eager checks to avoid adding obligations when they refer to types that reference `[type error]` in order to reduce unneded errors.
2019-09-22Point at correct span for parenthesized typesEsteban Küber-5/+5
2019-09-22On obligation errors point at the unfulfilled binding when possibleEsteban Küber-3/+3
2019-09-22Point at definition when misusing ADTEsteban Küber-0/+3
When given `struct Foo(usize)` and using it as `Foo {}` or `Foo`, point at `Foo`'s definition in the error.
2019-09-22Fixes #63962. Hint about missing tuple parentheses in patternsSam Radhakrishan-4/+19
2019-09-19When possible point at argument causing item obligation failureEsteban Küber-2/+2
2019-09-14Rollup merge of #64290 - Mark-Simulacrum:span-no-main, r=estebankMazdak Farrokhzad-3/+5
Provide a span if main function is not present in crate Unfortunately, the diagnostic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note. Tests are already updated for this change, so a dedicated test is not added. Resolves #36561.
2019-09-14Provide a span if main function is not present in crateMark Rousskov-3/+5
Unfortunately, the diagnotic machinery does not cope well with an empty span which can happen if the crate is empty, in which case we merely set a spanless note.
2019-09-12Auto merge of #64360 - varkor:foreign-items-diagnostic-const-generics, ↵bors-2/+2
r=cramertj Correct the polymorphic extern fn error for const parameters Before, any polymorphism on extern functions was assumed to be type polymorphism.
2019-09-11Make wording less confusingvarkor-2/+2
2019-09-08Tests: No longer emitting 0008, E0301, E0302.Mazdak Farrokhzad-36/+0
2019-09-08Update tests wrt. bind_by_by_move_pattern_guards stabilization.Mazdak Farrokhzad-39/+5
2019-09-06Rollup merge of #64161 - estebank:point-variant, r=CentrilMazdak Farrokhzad-0/+9
Point at variant on pattern field count mismatch
2019-09-04Point at variant on pattern field count mismatchEsteban Küber-0/+9
2019-09-02account for DUMMY_SP and correct wordingEsteban Küber-1/+1
2019-09-02On object safety violation, point at source when possibleEsteban Küber-12/+13
2019-09-02Refer to "`self` type" instead of "receiver type"Esteban Küber-4/+4
2019-08-31Use span label instead of note for cause in E0631Esteban Küber-27/+15
2019-08-21improve diagnostics: break/continue wrong contextArtem Varaksa-3/+5
2019-08-17Move type parameter shadowing errors to resolveMatthew Jasper-6/+6
For some reason type checking did this. Further it didn't consider hygiene.