summary refs log tree commit diff
path: root/src/test/ui/bad
AgeCommit message (Collapse)AuthorLines
2020-11-07Implement destructuring assignment for tuplesFabian Zaiser-16/+37
Co-authored-by: varkor <github@varkor.com>
2020-09-09Rollup merge of #75984 - kornelski:typeormodule, r=matthewjasperTyler Mandry-6/+6
Improve unresolved use error message "use of undeclared type or module `foo`" doesn't mention that it could be a crate. This error can happen when users forget to add a dependency to `Cargo.toml`, so I think it's important to mention that it could be a missing crate. I've used a heuristic based on Rust's naming conventions. It complains about an unknown type if the ident starts with an upper-case letter, and crate or module otherwise. It seems to work very well. The expanded error help covers both an unknown type and a missing crate case.
2020-09-02pretty: trim paths of unique symbolsDan Aloni-11/+11
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-09-01Clarify message about unresolved useKornel-6/+6
2020-08-14Tweak output of E0225Esteban Küber-5/+5
When encountering multiple non-auto trait bounds suggest creating a new trait and explain what auto-traits are.
2020-07-27mv std libs to library/mark-1/+1
2020-07-14Remove redundant explanatory `note` for type parametersEsteban Küber-1/+0
2020-07-14Remove `Sized` `on_unimplemented` noteEsteban Küber-2/+0
2020-04-11rustc: Add a warning count upon completionRoccoDev-0/+2
2020-04-08Use `PredicateObligation`s instead of `Predicate`sEsteban Küber-1/+5
Keep more information about trait binding failures.
2020-03-29Tweak `suggest_constraining_type_param`Esteban Küber-4/+3
Some of the bound restriction structured suggestions were incorrect while others had subpar output.
2020-02-09Improve reporting errors and suggestions for trait boundsPatryk Wychowaniec-2/+5
2020-01-24Normalise notes with the/isvarkor-2/+2
2020-01-05Add backticks to various diagnosticsvarkor-6/+6
2019-12-23Add new folder for destructuring assignment testsvarkor-148/+1
2019-12-23Add span information to `ExprKind::Assign`varkor-18/+18
2019-12-23Recognise nested tuples/arrays/structsvarkor-1/+16
2019-12-23Add note about destructuring assignmentsvarkor-0/+135
2019-12-23Improve invalid assignment errorvarkor-16/+26
2019-12-21rework run-fail and support check,build-failMazdak Farrokhzad-3/+5
2019-11-18Remove E0308 note when primary label has all infoEsteban Küber-5/+0
2019-11-18Specific labels when referring to "expected" and "found" typesEsteban Küber-10/+10
2019-11-14Fix ui tests with better error code usageGuillaume Gomez-0/+1
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+1
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-10-15Use structured suggestion for restricting boundsEsteban Küber-1/+2
When a trait bound is not met and restricting a type parameter would make the restriction hold, use a structured suggestion pointing at an appropriate place (type param in param list or `where` clause). Account for opaque parameters where instead of suggesting extending the `where` clause, we suggest appending the new restriction: `fn foo(impl Trait + UnmetTrait)`.
2019-07-19normalize use of backticks in compiler messages for librustc_metadataSamy Kacimi-2/+2
https://github.com/rust-lang/rust/issues/60532
2019-07-17normalize use of backticks in compiler messages for librustc/lintSamy Kacimi-2/+2
https://github.com/rust-lang/rust/issues/60532
2019-06-16compiletest: Remove `skip-codegen`Vadim Petrochenkov-4/+3
2019-05-29Update ui test suite to use dynmemoryruins-14/+14
2019-05-20Addressed more points raised in review.Alexander Regueiro-2/+5
2019-05-20Update tests.Alexander Regueiro-1/+3
2019-04-22Remove double trailing newlinesvarkor-1/+0
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-9/+8
2019-04-17Resolve inconsistency in error messages between "parameter" and "variable".Eduard-Mihai Burtescu-1/+1
2019-03-23Swap primary/secondary spans for E0458Esteban Küber-2/+2
2019-03-15rustc: pass Option<&Substs> and Namespace around in ty::item_path.Eduard-Mihai Burtescu-1/+1
2019-03-11Update testsVadim Petrochenkov-15/+15
2019-02-11Use hidden suggestions for unused imports lintEsteban Küber-2/+2
2019-02-11Auto merge of #56645 - pietroalbini:fix-unused-imports, r=estebankbors-2/+2
Initial implementation of rustfixable unused_imports lint This PR adds the initial implementation of rustfixable `unused_imports` lint. The implementation works, but rustfix is not able to apply all the suggestions until https://github.com/rust-lang/rust/issues/53934 is fixed. It also needs https://github.com/rust-lang/rust/pull/58296 to hide the suggested note since it's really useless. cc https://github.com/rust-lang/rust/issues/47888 <details><summary><code>cargo fix</code> in action on the <code>unused_imports</code> lint</summary> ![screenshot from 2018-12-09 15-49-01](https://user-images.githubusercontent.com/2299951/49698874-3a026080-fbca-11e8-9bf1-24060b6c59c8.png) </details>
2019-02-08unused_imports: update testsPietro Albini-2/+2
2019-02-07Make name resolution handle consts in GenericParamsFromOuterFunction properlyvarkor-5/+5
2019-01-12Auto merge of #57234 - Centril:const-stabilizations-2, r=oli-obkbors-1/+1
Const-stabilize `const_int_ops` + `const_ip` r? @oli-obk ## Note for relnotes: This PR includes https://github.com/rust-lang/rust/pull/57105. I've added T-lang since this affects intrinsics and the operational semantics of Rust's `const fn` fragment. ## Stable APIs proposed for constification + `const_int_ops`: + `count_ones` + `count_zeros` + `leading_zeros` + `trailing_zeros` + `swap_bytes` + `from_be` + `from_le` + `to_be` + `to_le` + `const_ip` + `Ipv4Addr::new` ## Unstable APIs constified + `const_int_conversion`: + `reverse_bits`
2019-01-05Rollup merge of #57249 - frewsxcv:frewsxcv-second-edition, r=KodrAuskennytm-2/+2
Fix broken links to second edition TRPL. Fixes https://github.com/rust-lang/rust/issues/57104. Remove `second-edition/` from TRPL hyperlinks.
2019-01-01Fix broken links to second edition TRPL.Corey Farwell-2/+2
Fixes https://github.com/rust-lang/rust/issues/57104.
2018-12-31Improve type mismatch error messagesYuning Zhang-2/+2
Replace "integral variable" with "integer" and replace "floating-point variable" with "floating-point number" to make the message less confusing.
2018-12-31const-stabilize const_int_ops + reverse_bitsMazdak Farrokhzad-1/+1
2018-12-25Remove licensesMark Rousskov-237/+47
2018-12-24make non_camel_case_types an early lintAndy Russell-2/+2
2018-11-18resolve: Avoid sentence breaks in diagnosticsVadim Petrochenkov-6/+6
2018-11-07Removed `#[rustc_error]` from tests that are all `// compile-pass`.Felix S. Klock II-12/+4
I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.)
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-12 16:28:54 +0000