about summary refs log tree commit diff
path: root/src/test/ui/editions
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-960/+0
2022-11-14Show a note where a macro failed to matchNilstrieb-0/+48
This shows a small note on what the macro matcher was currently processing to aid with "no rules expected the token X" errors.
2022-10-01bless ui testsMaybe Waffle-2/+2
2022-06-01Mention filename in suggestion when it differs from primary spanEsteban Küber-0/+2
2022-03-07diagnostics: only talk about `Cargo.toml` if running under CargoMichael Howell-6/+6
Fixes #94646
2022-01-27Improve suggestion for escaping reserved keywordsNoah Lev-12/+12
2021-12-04Use multipart suggestions.Camille GILLOT-1/+1
2021-12-04Lint bare traits in AstConv.Camille GILLOT-4/+9
2021-11-18Move some tests to more reasonable directoriesCaio-0/+70
2021-11-14Move some tests to more reasonable directoriesCaio-0/+70
2021-11-10Fix trait object error codeJimmy Envall-2/+2
2021-11-06Move some tests to more reasonable directoriesCaio-0/+15
2021-10-15Bless testsCameron Steffen-3/+3
2021-09-04Fix 2021 `dyn` suggestion that used code as labelNoah Lev-0/+21
The arguments to `span_suggestion` were in the wrong order, so the error looked like this: error[E0783]: trait objects without an explicit `dyn` are deprecated --> src/test/ui/editions/dyn-trait-sugg-2021.rs:10:5 | 10 | Foo::hi(123); | ^^^ help: <dyn Foo>: `use `dyn`` Now the error looks like this, as expected: error[E0783]: trait objects without an explicit `dyn` are deprecated --> src/test/ui/editions/dyn-trait-sugg-2021.rs:10:5 | 10 | Foo::hi(123); | ^^^ help: use `dyn`: `<dyn Foo>` This issue was only present in the 2021 error; the 2018 lint was correct.
2021-08-30Update test output for stable Rust 2021.Mara Bos-6/+6
2021-08-11Modify structured suggestion outputEsteban Küber-6/+6
* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-08-04Remove trailing whitespace from error messagesFabian Wolff-2/+2
2021-06-25Address PR feedbackRyan Levick-2/+2
2021-06-25Change how edition based future compatibility warnings are handledRyan Levick-2/+2
2021-06-21Mark some edition tests as check-passAris Merchant-4/+4
2021-05-12Show macro name in 'this error originates in macro' messageAaron Hill-5/+5
When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-03-07diagnostics: Differentiate between edition meanings of ::foo in resolve ↵Manish Goregaokar-1/+1
diagnostics (for bare `::foo`)
2021-01-18Improve unknown external crate errorRyan Levick-1/+1
2020-12-31Consistently call editions "Rust 20xx" in messages.Mara Bos-8/+8
2020-12-31Add edition 2021.Mara Bos-6/+6
2020-05-05Detect errors caused by `async` block in 2015 editionEsteban Küber-0/+71
2020-04-23Moving more build-pass tests to check-passVal Markovic-2/+2
One or two tests became build-pass without the FIXME because they really needed build-pass (were failing without it). Helps with #62277
2020-04-11rustc: Add a warning count upon completionRoccoDev-0/+5
2020-03-24expand: address review commentsMazdak Farrokhzad-28/+34
2020-03-24nix panictry! in ParserAnyMacro::makeMazdak Farrokhzad-14/+46
2020-03-10rustc_errors: Use ensure_source_file_source_present where necessary.Ana-Maria Mihalache-4/+4
2020-03-10--bless some testsMazdak Farrokhzad-10/+10
2020-02-06rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.Eduard-Mihai Burtescu-5/+5
2020-02-06rustc: rename -Zexternal-macro-backtrace to -Zmacro-backtrace.Eduard-Mihai Burtescu-5/+5
2020-01-24Normalise notes with the/isvarkor-2/+2
2019-11-06Remove "here" from "expected one of X here"Esteban Küber-2/+2
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+4
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-09-28Upgrade async/await to "used" keywords.Eric Huss-18/+18
2019-07-17normalize use of backticks in compiler messages for librustc/lintSamy Kacimi-2/+2
https://github.com/rust-lang/rust/issues/60532
2019-07-15pprust: Use `print_mac_common` for delimited token groupsVadim Petrochenkov-10/+10
2019-07-03Migrate compile-pass annotations to build-passYuki Okushi-6/+6
2019-05-24Move async/await tests to test/ui/async-awaitvarkor-91/+0
2019-04-23Stabilize futures_apiTaylor Cramer-1/+1
2019-04-23Update ui testsvarkor-3/+3
2019-04-23Remove unnecessary ignore-tidy-linelengthvarkor-2/+0
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-2/+1
2019-03-12resolve: Simplify import resolution for mixed 2015/2018 edition modeVadim Petrochenkov-57/+7
2019-03-11Update testsVadim Petrochenkov-31/+31
2019-02-27Rollup merge of #58678 - doctorn:refuse-async-fn-2015-edition, r=varkorMazdak Farrokhzad-0/+92
Deny `async fn` in 2015 edition This commit prevents code using `async fn` from being compiled in Rust 2015 edition. Compiling code of the form: ```rust async fn foo() {} ``` Will now result in the error: ``` error[E0670]: `async fn` is not permitted in the 2015 edition --> async.rs:1:1 | 1 | async fn foo() {} | ^^^^^ error: aborting due to error For more information about an error, try `rustc --explain E0670`. ``` This resolves #58652 and also resolves #53714. r? @varkor
2019-02-24Deny `async fn` in 2015 editionNathan Corbyn-0/+92
Fix style issues and update diagnostic messages Update src/librustc_passes/diagnostics.rs Co-Authored-By: doctorn <me@nathancorbyn.com> Deny nested `async fn` in Rust 2015 edition Deny nested `async fn` in Rust 2015 edition Deny nested `async fn` in Rust 2015 edition
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-23 22:45:33 +0000