about summary refs log tree commit diff
path: root/src/test/ui/error-codes
AgeCommit message (Collapse)AuthorLines
2019-06-10Implement RFC 2645 (transparent enums and unions)Michael Bradshaw-4/+4
Tracking issue: #60405
2019-06-03Update tests for changes to cannot move errorsMatthew Jasper-2/+5
2019-06-02Rollup merge of #61438 - estebank:generics-span, r=varkorMazdak Farrokhzad-4/+25
Point at individual type args on arg count mismatch - Point at individual type arguments on arg count mismatch - Make generics always have a valid span, even when there are no args - Explain that `impl Trait` introduces an implicit type argument Fix #55991.
2019-06-02Add error for pattern-matching on arrays without a fixed sizevarkor-0/+26
2019-06-01Point at individual type arguments on arg count mismatchEsteban Küber-4/+25
2019-05-29Auto merge of #61203 - memoryruins:bare_trait_objects, r=Centrilbors-42/+42
Warn on bare_trait_objects by default The `bare_trait_objects` lint is set to `warn` by default. Most ui tests have been updated to use `dyn` to avoid creating noise in stderr files. r? @Centril cc #54910
2019-05-29Update ui test suite to use dynmemoryruins-42/+42
2019-05-25Reword malformed attribute input diagnosticsEsteban Küber-2/+2
- Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error - Use consistend error message: "malformed `attrname` attribute input" - Provide suggestions when possible - Move note/help to label/suggestion - Use consistent wording "ill-formed" -> "malformed" - Move diagnostic logic out of parser
2019-05-24Move error code tests to error code foldervarkor-0/+591
2019-05-20Addressed more points raised in review.Alexander Regueiro-8/+14
2019-05-20Addressed points raised in review.Alexander Regueiro-2/+2
2019-05-20Update tests.Alexander Regueiro-3/+7
2019-05-20Update tests.Alexander Regueiro-2/+17
2019-05-12Change compare mode to use -Zborrowck=mirMatthew Jasper-0/+24
2019-05-02fix typoEsteban Küber-2/+2
2019-04-23Rollup merge of #60169 - varkor:tidy-unnecessary-ignore-newline, r=kennytmMazdak Farrokhzad-3/+1
Warn when ignore-tidy-linelength is present, but no lines are too long It's easy for a `// ignore-tidy-linelength` to be added when there is a genuine need to ignore a file's line length, but then after refactoring the need is gone, but the tidy directive is not removed. This means that in the future, further editing may accidentally add unnecessarily long lines. This change forces `// ignore-tidy-linelength` to be used exactly when necessary, to make sure such changes are intentional.
2019-04-23Update ui testsvarkor-1/+1
2019-04-23Remove unnecessary ignore-tidy-linelengthvarkor-2/+0
2019-04-22Never stop due to errors before borrow checkingEsteban Küber-7/+45
2019-04-22update tests for migrate mode by defaultMatthew Jasper-241/+58
2019-04-19Emit specific error for struct literal in conditionsEsteban Küber-43/+17
2019-04-19Rollup merge of #60052 - varkor:unused-parameter-diagnostic, r=estebankMazdak Farrokhzad-1/+1
Correct unused parameter diagnostic The message was incorrect for unused lifetime parameters. There's no need to be specific.
2019-04-18Update testsvarkor-1/+1
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-23/+17
2019-04-17Resolve inconsistency in error messages between "parameter" and "variable".Eduard-Mihai Burtescu-2/+2
2019-04-14Rollup merge of #59675 - SimonSapin:stable-alloc, r=alexcrichtonMazdak Farrokhzad-5/+3
Stabilize the `alloc` crate. This implements RFC 2480: * https://github.com/rust-lang/rfcs/pull/2480 * https://github.com/rust-lang/rfcs/blob/master/text/2480-liballoc.md Closes https://github.com/rust-lang/rust/issues/27783
2019-04-12Stabilize the `alloc` crate.Simon Sapin-5/+3
This implements RFC 2480: * https://github.com/rust-lang/rfcs/pull/2480 * https://github.com/rust-lang/rfcs/blob/master/text/2480-liballoc.md Closes https://github.com/rust-lang/rust/issues/27783
2019-04-11Reword tracking issue noteEsteban Küber-3/+3
2019-04-10Tweak unstable diagnostic outputEsteban Küber-4/+9
2019-03-28Rollup merge of #59408 - euclio:compiletest-normalization, r=oli-obkMazdak Farrokhzad-1/+1
compiletest: make path normalization smarter Fixes #59109.
2019-03-26Rollup merge of #59150 - estebank:type-ascription, r=varkorMazdak Farrokhzad-0/+16
Expand suggestions for type ascription parse errors Fix #51222. CC #48016, #47666, #54516, #34255.
2019-03-25compiletest: make path normalization smarterAndy Russell-1/+1
2019-03-23Hide obvious suggestion from cli outputEsteban Küber-4/+2
2019-03-23Swap primary/secondary spans for E0458Esteban Küber-2/+2
2019-03-23Swap const evaluation lint spans to point at problem in primary spanEsteban Küber-2/+2
2019-03-23Tweak spans for E0599Esteban Küber-1/+1
2019-03-22Reword type ascription note to reduce verbosityEsteban Küber-12/+2
2019-03-22Review commentEsteban Küber-2/+2
2019-03-22Expand suggestions for type ascription parse errorsEsteban Küber-0/+26
2019-03-20Update testsvarkor-4/+4
2019-03-11Update tests that don't run on my platformVadim Petrochenkov-16/+0
2019-03-11Update NLL testsVadim Petrochenkov-19/+19
2019-03-11Update testsVadim Petrochenkov-200/+200
2019-03-02Reword error messageEsteban Küber-1/+1
2019-03-02Point at enum definition when match patterns are not exhaustiveEsteban Küber-7/+12
``` error[E0004]: non-exhaustive patterns: type `X` is non-empty --> file.rs:9:11 | 1 | / enum X { 2 | | A, | | - variant not covered 3 | | B, | | - variant not covered 4 | | C, | | - variant not covered 5 | | } | |_- `X` defined here ... 9 | match x { | ^ | = help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms error[E0004]: non-exhaustive patterns: `B` and `C` not covered --> file.rs:11:11 | 1 | / enum X { 2 | | A, 3 | | B, 4 | | C, | | - not covered 5 | | } | |_- `X` defined here ... 11 | match x { | ^ patterns `C` not covered ``` When a match expression doesn't have patterns covering every variant, point at the enum's definition span. On a best effort basis, point at the variant(s) that are missing. This does not handle the case when the missing pattern is due to a field's enum variants: ``` enum E1 { A, B, C, } enum E2 { A(E1), B, } fn foo() { match E2::A(E1::A) { E2::A(E1::B) => {} E2::B => {} } //~^ ERROR `E2::A(E1::A)` and `E2::A(E1::C)` not handled } ``` Unify look between match with no arms and match with some missing patterns. Fix #37518.
2019-02-27Rename variadic to c_variadicDan Robertson-2/+2
Function signatures with the `variadic` member set are actually C-variadic functions. Make this a little more explicit by renaming the `variadic` boolean value, `c_variadic`.
2019-02-27Support defining C compatible variadic functionsDan Robertson-6/+6
Add support for defining C compatible variadic functions in unsafe rust with extern "C".
2019-02-14rustc_mir: split qualify_consts' checking and value qualification.Eduard-Mihai Burtescu-16/+16
2019-02-07Make name resolution handle consts in GenericParamsFromOuterFunction properlyvarkor-8/+8
2019-02-07Update testsvarkor-1/+1
Co-Authored-By: Gabriel Smith <yodaldevoid@users.noreply.github.com>
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-25 12:11:59 +0000