about summary refs log tree commit diff
path: root/src/test/ui/missing
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-432/+0
2022-11-03Stabilize default_alloc_error_handlerAmanieu d'Antras-29/+0
Closes #66741
2022-06-16 fix one more case of trailing spaceklensy-1/+1
2022-06-13Improve parsing errors and suggestions for bad if statementsMichael Goulet-5/+12
2022-06-02add new `emit_inference_failure_err`lcnr-5/+4
2022-05-20report ambiguous type parameters when their parents are impl or fnTakayuki Maeda-0/+6
fix ci error emit err for `impl_item`
2022-04-04diagnostics: use correct span for const genericsMichael Howell-2/+2
Fixes #95616
2022-03-05Auto merge of #93142 - estebank:missing-main, r=wesleywiserbors-2/+2
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
2022-03-05Do not point at whole file missing `fn main`Esteban Kuber-2/+2
Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
2022-03-03Cleanup feature gates.Camille GILLOT-2/+2
2022-02-28Tweak diagnosticsEsteban Kuber-4/+6
* Recover from invalid `'label: ` before block. * Make suggestion to enclose statements in a block multipart. * Point at `match`, `while`, `loop` and `unsafe` keywords when failing to parse their expression. * Do not suggest `{ ; }`. * Do not suggest `|` when very unlikely to be what was wanted (in `let` statements).
2021-12-14Suggest to specify a target triple when eh_personality lang item is missingLucas Kent-1/+1
2021-12-10bless testsEllen-8/+8
2021-12-10update testsEllen-3/+0
2021-10-03Practice diagnostic message conventionHirochika Matsumoto-3/+3
2021-08-11Modify structured suggestion outputEsteban Küber-13/+13
* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-05-07Fix impl type parameter suggestion involving constsmibac138-9/+49
2021-05-06Expand impl type parameter suggestion testsmibac138-0/+103
2021-02-20Fix suggestion span and move suggestions into new subwindow.Reese Williams-3/+6
2021-02-14Clarify error message and remove pretty printing in help suggestions.Reese Williams-1/+3
2020-11-19Regroup many usefulness-related test in the same folderNadrieril-34/+0
2020-10-17Rollup merge of #75209 - Hirrolot:suggest-macro-imports, r=estebankYuki Okushi-0/+3
Suggest imports of unresolved macros Closes https://github.com/rust-lang/rust/issues/75191.
2020-10-02Implement Make `handle_alloc_error` default to panic (for no_std + liballoc)Harald Hoyer-1/+3
Related: https://github.com/rust-lang/rust/issues/66741 Guarded with `#![feature(default_alloc_error_handler)]` a default `alloc_error_handler` is called, if a custom allocator is used and no other custom `#[alloc_error_handler]` is defined. The panic message does not contain the size anymore, because it would pull in the fmt machinery, which would blow up the code size significantly.
2020-09-30Re-run tests with --blessTemirkhan Myrzamadi-0/+3
2020-09-02pretty: trim paths of unique symbolsDan Aloni-4/+4
If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-07-12Detect tuple struct incorrectly used as struct patEsteban Küber-15/+5
2020-04-16Fixed issue with self: &Box<Self>Duddino-2/+4
2020-04-16fixed missing trait method suggests incorrect code (self parameter not named ↵Duddino-2/+8
self)
2020-03-27non-exhastive diagnostic: add note re. scrutinee typeMazdak Farrokhzad-0/+1
2020-02-13macro_legacy_warnings -> errorMazdak Farrokhzad-36/+0
2020-02-09Auto merge of #68689 - estebank:where-clause-sugg-missing-fn, r=varkorbors-1/+1
When suggesting associated fn with type parameters, include in the structured suggestion Address #50734. ``` error[E0046]: not all trait items implemented, missing: `foo`, `bar`, `baz` --> file.rs:14:1 | 14 | impl TraitA<()> for S { | ^^^^^^^^^^^^^^^^^^^^^ missing `foo`, `bar`, `baz` in implementation | = help: implement the missing item: `fn foo<T>(_: T) -> Self where T: TraitB, TraitB::Item = A { unimplemented!() }` = help: implement the missing item: `fn bar<T>(_: T) -> Self { unimplemented!() }` = help: implement the missing item: `fn baz<T>(_: T) -> Self where T: TraitB, <T as TraitB>::Item: std::marker::Copy { unimplemented!() }` ``` It doesn't work well for associated types with `ty::Predicate::Projection`s as we need to resugar `T: Trait, Trait::Assoc = K` → `T: Trait<Assoc = K>`.
2020-02-08review commentEsteban Küber-1/+1
2020-02-06rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.Eduard-Mihai Burtescu-0/+2
2019-12-23more recovery in if-parsingMazdak Farrokhzad-2/+2
2019-12-21Require issue = "none" over issue = "0" in unstable attributesRoss MacArthur-1/+1
2019-12-14Indicate origin of where type parameter for uninferred typesOhad Ravid-1/+1
2019-12-11Add more context for type parametersEsteban Küber-1/+1
2019-11-18Surround types with backticks in type errorsEsteban Küber-1/+1
2019-11-18Remove E0308 note when primary label has all infoEsteban Küber-3/+0
2019-11-18review comments: tweak prefix stringsEsteban Küber-2/+2
2019-11-08Rollup merge of #66007 - estebank:remove-here, r=CentrilMazdak Farrokhzad-3/+3
Remove "here" from "expected one of X here"
2019-11-06Remove "here" from "expected one of X here"Esteban Küber-3/+3
2019-11-06Suggest missing item from `trait` in `impl`Esteban Küber-3/+3
2019-09-15resolve: Remove `!` from "cannot find" diagnostics for macrosVadim Petrochenkov-2/+2
2019-09-14Provide a span if main function is not present in crateMark Rousskov-1/+3
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-06Fixed grammar/style in error messages and reblessed tests.Alexander Regueiro-2/+2
2019-08-09review comments: typo and rewordingEsteban Küber-1/+1
2019-08-09review comment: review wording or missing return errorEsteban Küber-1/+1
2019-08-09Tweak wording of fn without explicit returnEsteban Küber-1/+1
2019-08-09Change wording for function without return valueEsteban Küber-1/+1
Fix #62677
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-16 01:49:03 +0000