about summary refs log tree commit diff
path: root/src/test/ui/rust-2018
AgeCommit message (Collapse)AuthorLines
2020-05-07reword "possible candidate" import suggestionAndy Russell-1/+1
2020-04-23Moving more build-pass tests to check-passVal Markovic-7/+7
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/+10
2020-03-07resolve: `directive` -> `import`Vadim Petrochenkov-2/+2
2020-02-06rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.Eduard-Mihai Burtescu-0/+4
2020-01-24Normalise notes with the/isvarkor-19/+19
2020-01-09Update testsVadim Petrochenkov-3/+42
2019-11-10Make error and warning annotations mandatory in UI testsTomasz Miąsko-10/+20
This change makes error and warning annotations mandatory in UI tests. The only exception are tests that use error patterns to match compiler output and don't have any annotations.
2019-11-04Use check-pass in ui tests where appropriateTomasz Miąsko-1/+1
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+69
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-13Bring attention to suggestions when the only difference is capitalizationEsteban Küber-1/+1
2019-09-30Fixed grammar in one diagnostic and blessed tests.Alexander Regueiro-3/+3
2019-09-09Rollup merge of #64054 - estebank:unused-import-is-to-eager, r=petrochenkovMazdak Farrokhzad-4/+4
Always emit unresolved import errors and hide unused import lint Fix https://github.com/rust-lang/rust/issues/63724. r? @petrochenkov
2019-09-08Give method not found a primary span labelEsteban Küber-3/+3
2019-09-08Always emit unresolved import errors and hide unused import lintEsteban Küber-4/+4
2019-08-10diagnostics: Describe crate root modules in `DefKind::Mod` as "crate"Vadim Petrochenkov-10/+10
2019-08-09Deprecate `try!` macroBO41-1/+3
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com> Co-Authored-By: Oliver Middleton <olliemail27@gmail.com>
2019-07-26Introduce built-in macros through libcoreVadim Petrochenkov-14/+7
2019-07-17normalize use of backticks in compiler messages for librustc/lintSamy Kacimi-8/+8
https://github.com/rust-lang/rust/issues/60532
2019-07-03Migrate compile-pass annotations to build-passYuki Okushi-16/+16
2019-06-18Improve the explicit_outlives_requirements lintMatthew Jasper-413/+3194
* Don't use Strings to compare parameters * Extend the lint to lifetime bounds * Extend the lint to enums and unions * Use the correct span for where clauses in tuple structs * Try to early-out where possible
2019-04-25Do not suggest use over extern crate w/ alias.David Wood-18/+20
This commit stops `unused_extern_crates` lints from occuring on `extern crate` statements that alias the crate as the suggestion to change to a `use` statement would result in the aliased name no longer being added to the prelude, thereby causing compilation errors if other imports expected this to be the case.
2019-04-22Update ui testsvarkor-5/+0
2019-04-22Remove double trailing newlinesvarkor-5/+0
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-1/+1
2019-04-14Rollup merge of #59675 - SimonSapin:stable-alloc, r=alexcrichtonMazdak Farrokhzad-6/+4
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-6/+4
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-10clarify what the item is in "not a module" errorAndy Russell-1/+1
2019-03-30Replace REDUNDANT_IMPORT with UNUSED_IMPORTSFabian Drinck-56/+10
2019-03-30Edit ui testsFabian Drinck-0/+1
2019-03-30Bless testsFabian Drinck-0/+46
2019-03-23Tweak spans for E0599Esteban Küber-3/+1
2019-03-16resolve: Account for new importable entitiesVadim Petrochenkov-0/+42
2019-03-11Update testsVadim Petrochenkov-40/+40
2019-03-09use structured suggestions for E0432Andy Russell-4/+7
2019-01-12Fix a hole in generic parameter import future-proofingVadim Petrochenkov-2/+8
Add some tests for buggy derive helpers
2019-01-12Stabilize `uniform_paths`Vadim Petrochenkov-79/+24
2019-01-12resolve: Prohibit use of imported tool modulesVadim Petrochenkov-6/+44
2019-01-12resolve: Prohibit use of imported non-macro attributesVadim Petrochenkov-4/+23
2019-01-12resolve: Assign `pub` and `pub(crate)` visibilities to `macro_rules` itemsVadim Petrochenkov-40/+13
2018-12-31Address review commentsEsteban Küber-1/+1
- Suggest raw ident escaping in all editions - Keep primary label in all cases
2018-12-31Suggest using raw identifiers in 2018 edition when using keywordsEsteban Küber-1/+5
2018-12-29Auto merge of #56225 - alexreg:type_alias_enum_variants, r=petrochenkovbors-2/+4
Implement RFC 2338, "Type alias enum variants" This PR implements [RFC 2338](https://github.com/rust-lang/rfcs/pull/2338), allowing one to write code like the following. ```rust #![feature(type_alias_enum_variants)] enum Foo { Bar(i32), Baz { i: i32 }, } type Alias = Foo; fn main() { let t = Alias::Bar(0); let t = Alias::Baz { i: 0 }; match t { Alias::Bar(_i) => {} Alias::Baz { i: _i } => {} } } ``` Since `Self` can be considered a type alias in this context, it also enables using `Self::Variant` as both a constructor and pattern. Fixes issues #56199 and #56611. N.B., after discussing the syntax for type arguments on enum variants with @petrochenkov and @eddyb (there are also a few comments on the [tracking issue](https://github.com/rust-lang/rust/issues/49683)), the consensus seems to be treat the syntax as follows, which ought to be backwards-compatible. ```rust Option::<u8>::None; // OK Option::None::<u8>; // OK, but lint in near future (hard error next edition?) Alias::<u8>::None; // OK Alias::None::<u8>; // Error ``` I do not know if this will need an FCP, but let's start one if so.
2018-12-29Auto merge of #57181 - petrochenkov:impice3, r=estebankbors-0/+12
resolve: Fix another ICE in import validation Imports are allowed to have ambiguous resolutions as long as all of them have same `Def`. As it turned out, it's possible for different `Module`s to have same `Def` when `extern crate` items are involved. Fixes https://github.com/rust-lang/rust/issues/56596
2018-12-29resolve: Fix another ICE in import validationVadim Petrochenkov-0/+12
2018-12-28resolve: Fix an ICE in import validationVadim Petrochenkov-0/+33
2018-12-26Fixed more tests.Alexander Regueiro-2/+4
2018-12-25Remove licensesMark Rousskov-690/+131
2018-12-24make non_camel_case_types an early lintAndy Russell-34/+46
2018-12-17Stabilize `underscore_imports`Vadim Petrochenkov-2/+2