about summary refs log tree commit diff
path: root/src/test/ui/issues/issue-28098.stderr
AgeCommit message (Collapse)AuthorLines
2022-05-28Move some tests to more reasonable placesCaio-77/+0
2021-11-20Do not mention associated items when they introduce an obligationEsteban Kuber-30/+0
2021-09-16Point at call span that introduced obligation for the argEsteban Kuber-4/+12
2021-07-19Various diagnostics clean ups/tweaksEsteban Küber-6/+30
* Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2020-10-06Fix tests from rebaseMatthew Jasper-3/+4
2020-10-06Separate bounds and predicates for associated/opaque typesMatthew Jasper-2/+3
2020-09-02pretty: trim paths of unique symbolsDan Aloni-10/+10
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.
2019-09-19When possible point at argument causing item obligation failureEsteban Küber-10/+26
2018-12-25Remove licensesMark Rousskov-6/+6
2018-10-09Reword `rustc_on_unimplemented` errors for `Iterator`Esteban Küber-12/+12
- Detect one element array of `Range` type, which is potentially a typo: `for _ in [0..10] {}` where iterating between `0` and `10` was intended. (#23141) - Suggest `.bytes()` and `.chars()` for `String`. - Suggest borrowing or `.iter()` on arrays (#36391) - Suggest using range literal when iterating on integers (#34353) - Do not suggest `.iter()` by default (#50773, #46806)
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+57