summary refs log tree commit diff
path: root/src/test/ui/object-safety
AgeCommit message (Collapse)AuthorLines
2020-10-20review commentsEsteban Küber-22/+22
2020-10-20Tweak "object unsafe" errorsEsteban Küber-91/+142
Fix #77598.
2020-10-06Check associated type bounds for object safety violationsMatthew Jasper-0/+26
2020-09-02pretty: trim paths of unique symbolsDan Aloni-9/+9
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-02-03Change wording for object unsafe because of assoc constEsteban Küber-2/+2
2020-02-02Point at reason in object unsafe trait with `Self` in supertraits or ↵Esteban Küber-4/+10
`where`-clause
2020-02-02Use more appropriate spans on object unsafe traits and provide structured ↵Esteban Küber-6/+12
suggestions when possible
2020-02-02Wording changes to object unsafe trait errorsEsteban Küber-18/+68
Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-02Slight rewording of diagnostic messageEsteban Küber-4/+4
2020-02-02Point at the `Sized` obligation in `where` clausesEsteban Küber-3/+6
2020-02-02Tweak `Self: Sized` restriction diagnostic outputEsteban Küber-3/+0
2020-02-02Point at `Sized` boundEsteban Küber-0/+6
2020-02-02Point at arguments or output when fn obligations come from them, or ident ↵Esteban Küber-16/+16
when they don't
2019-10-22RFC 2027: "first draft" of implementationMathias Blikstad-25/+183
These are a squashed series of commits.
2019-09-02account for DUMMY_SP and correct wordingEsteban Küber-2/+2
2019-09-02On object safety violation, point at source when possibleEsteban Küber-12/+18
2019-09-02Refer to "`self` type" instead of "receiver type"Esteban Küber-1/+1
2019-07-03Migrate compile-pass annotations to build-passYuki Okushi-2/+2
2019-05-29Update ui test suite to use dynmemoryruins-52/+52
2019-04-22update tests for migrate mode by defaultMatthew Jasper-11/+2
2019-03-11Update NLL testsVadim Petrochenkov-1/+1
2019-03-11Update testsVadim Petrochenkov-1/+1
2018-12-25Remove licensesMark Rousskov-122/+12
2018-11-07Removed `#[rustc_error]` from tests that are all `// compile-pass`.Felix S. Klock II-24/+6
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.)
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+527