about summary refs log tree commit diff
path: root/src/test/ui/resolve
AgeCommit message (Collapse)AuthorLines
2020-03-04resolve, inconsistent binding mode: tweak wording.Mazdak Farrokhzad-49/+50
2020-02-28Rollup merge of #69539 - Centril:fix-69401, r=petrochenkovMazdak Farrokhzad-0/+15
late resolve, visit_fn: bail early if there's no body. Fixes https://github.com/rust-lang/rust/issues/69401 which was injected by https://github.com/rust-lang/rust/commit/b2c6eeb713d4cf9b35b7dda6ff2b0274e7f24684 in https://github.com/rust-lang/rust/pull/68788. r? @petrochenkov
2020-02-28Rollup merge of #69452 - Centril:typeck-pat, r=estebankMazdak Farrokhzad-5/+22
typeck: use `Pattern` obligation cause more for better diagnostics r? @estebank
2020-02-28late resolve, visit_fn: bail early if there's no body.Mazdak Farrokhzad-0/+15
2020-02-26Rollup merge of #67637 - Mark-Simulacrum:primitive-mod, r=dtolnayDylan DPC-0/+5
Add primitive module to libcore This re-exports the primitive types from libcore at `core::primitive` to allow macro authors to have a reliable location to use them from. Fixes #44865
2020-02-25check_pat_path: use pattern_causeMazdak Farrokhzad-1/+3
2020-02-25improve or-pattern type consistency diagnosticsMazdak Farrokhzad-4/+19
2020-02-11On mismatched argument count point at argumentsEsteban Küber-3/+5
2020-02-06Add primitive module to libcore/stdMark Rousskov-0/+5
This re-exports the primitive types from libcore at `core::primitive` to allow macro authors to have a reliable location to use them from.
2020-02-02Wording changes to object unsafe trait errorsEsteban Küber-1/+1
Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-02Point at arguments or output when fn obligations come from them, or ident ↵Esteban Küber-2/+2
when they don't
2020-02-02Do not suggest things named underscoreYuki Okushi-0/+30
2020-01-16resolve: Point at the private item definitions in privacy errorsVadim Petrochenkov-10/+70
2020-01-12Update `output-default.json` and rustdoc testvarkor-1/+1
2020-01-12Appease tidyvarkor-1/+2
2020-01-12Diagnostics should not end with a full stopvarkor-3/+3
2020-01-10Ignore platforms that can't point to stdEsteban Küber-8/+12
2020-01-10Use `def_span` to minimize definition span to first line when possibleEsteban Küber-10/+4
2020-01-10Point at the span for the definition of crate foreign ADTsEsteban Küber-2/+13
2020-01-03tweak wording of mismatched delimiter errorsAndy Russell-9/+9
2019-12-30refactor and fix this-expression-has-type noteMazdak Farrokhzad-0/+8
2019-12-11resolve: Always resolve visibilities on impl itemsVadim Petrochenkov-0/+34
2019-11-21Point at type in `let` assignment on type errorsEsteban Küber-12/+15
2019-11-18Surround types with backticks in type errorsEsteban Küber-4/+4
2019-11-18Remove E0308 note when primary label has all infoEsteban Küber-9/+0
2019-11-18Specific labels when referring to "expected" and "found" typesEsteban Küber-7/+7
2019-11-08Rollup merge of #66007 - estebank:remove-here, r=CentrilMazdak Farrokhzad-1/+1
Remove "here" from "expected one of X here"
2019-11-06Remove "here" from "expected one of X here"Esteban Küber-1/+1
2019-11-04Use check-pass in ui tests where appropriateTomasz Miąsko-1/+1
2019-10-31update ui testsGuillaume Gomez-0/+1
2019-10-30Update ui testsGuillaume Gomez-1/+1
2019-10-29Change E0741 into E0742Guillaume Gomez-2/+2
2019-10-29Update ui testsGuillaume Gomez-2/+3
2019-10-27Point at local similarly named element and tweak references to variantsEsteban Küber-27/+122
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/+29
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/+14
2019-10-17Refer to "associated functions" instead of "static methods"Esteban Küber-2/+2
2019-10-15Rollup merge of #65308 - GuillaumeGomez:long-err-explanation-E0574, ↵Tyler Mandry-0/+1
r=matthewjasper Add long error explanation for E0574 Part of #61137.
2019-10-14Rollup merge of #65398 - estebank:capitalization-only, r=varkorTyler Mandry-3/+3
Bring attention to suggestions when the only difference is capitalization CC #65386.
2019-10-14Use heuristics for capitalization warning in suggestionsEsteban Küber-1/+1
2019-10-13Bring attention to suggestions when the only difference is capitalizationEsteban Küber-4/+4
2019-10-13Update ui testsGuillaume Gomez-0/+1
2019-10-11resolve: shorten wording on private constructor errorDan Aloni-6/+6
2019-10-11resolve: fix error title regarding private constructorsDan Aloni-12/+12
The constructor is private, not the type. Idea credit to @petrochenkov, discussed at #65153
2019-10-10Auto merge of #65153 - da-x:issue-58017, r=petrochenkovbors-10/+20
Improve message when attempting to instantiate tuple structs with private fields Fixes #58017, fixes #39703. ``` error[E0603]: tuple struct `Error` is private --> main.rs:22:16 | 2 | pub struct Error(usize, pub usize, usize); | ----- ----- field is private | | | field is private ... 22 | let x = a::Error(3, 1, 2); | ^^^^^ | = note: a tuple struct constructor is private if any of its fields is private ```
2019-10-09resolve: Use field spans for reporting the private constructor errorVadim Petrochenkov-10/+20
2019-10-08resolve: prohibit foreign statics w/ genericsDavid Wood-0/+104
This commit modifies resolve to disallow foreign statics that use parent generics. `improper_ctypes` is not written to support type parameters, as these are normally disallowed before the lint is run. Thus, type parameters in foreign statics must be prohibited before the lint. The only other case where this *could* have occured is in functions, but typeck prohibits this with a "foreign items may not have type parameters" error - a similar error did not exist for statics, because statics cannot have type parameters, but they can use any type parameters that are in scope (which isn't the case for functions). Signed-off-by: David Wood <david@davidtw.co>
2019-09-29Rollup merge of #64691 - estebank:unexpected-variant, r=CentrilMazdak Farrokhzad-12/+51
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-28Auto merge of #64455 - GuillaumeGomez:long-error-explanation-E0531, r=Centrilbors-1/+1
Add Long error explanation for E0531 Part of #61137.
2019-09-25update ui testsGuillaume Gomez-1/+1
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 20:50:57 +0000