about summary refs log tree commit diff
path: root/src/test/ui/codemap_tests/tab_3.stderr
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-22/+0
2022-12-25Remove redundant clone suggestionEsteban Küber-4/+0
2022-12-25Create new inference contextEsteban Küber-0/+4
2022-12-13Clarify what "this" meansOli Scherer-1/+1
2022-12-13Make some diagnostics not depend on the source of what they reference being ↵Oli Scherer-3/+0
available
2022-11-23Suggest `.clone()` or `ref binding` on E0382Esteban Küber-0/+4
2022-07-19Mention first and last macro in backtraceMichael Goulet-1/+1
2021-10-29Fix a format_args span to be expansionCameron Steffen-0/+1
2021-01-08Change wording of noteAaron Hill-1/+1
2020-09-02pretty: trim paths of unique symbolsDan Aloni-1/+1
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-07-27mv std libs to library/mark-1/+1
2020-06-26Explain move errors that occur due to method calls involving `self`Aaron Hill-1/+7
This is a re-attempt of #72389 (which was reverted in #73594) Instead of using `ExpnKind::Desugaring` to represent operators, this PR checks the lang item directly.
2020-06-22Revert "Rollup merge of #72389 - Aaron1011:feature/move-fn-self-msg, ↵Aaron Hill-7/+1
r=nikomatsakis" This reverts commit 372cb9b69c76a042d0b9d4b48ff6084f64c84a2c, reversing changes made to 5c61a8dc34c3e2fc6d7f02cb288c350f0233f944.
2020-06-11Use `fn_span` to point to the actual method callAaron Hill-1/+1
2020-06-11Explain move errors that occur due to method calls involving `self`Aaron Hill-1/+7
2019-04-22update tests for migrate mode by defaultMatthew Jasper-4/+4
2019-03-11Update testsVadim Petrochenkov-1/+1
2018-12-25Remove licensesMark Rousskov-1/+1
2018-03-14update testsGuillaume Gomez-1/+1
2018-02-26Update UI testsVadim Petrochenkov-1/+1
2018-02-26Update UI testsVadim Petrochenkov-2/+2
2018-02-25Update ui testsGuillaume Gomez-0/+1
2017-11-24Display `\t` in diagnostics code as four spacesEsteban Küber-5/+5
2017-11-24Merge cfail and ui tests into ui testsOliver Schneider-1/+1
2017-09-07Fix mispositioned error indicatorsest31-0/+13
Fixes #38384 Most of the Rust community uses 4 spaces for indentation, but there are also tab users of Rust (including myself!). This patch fixes a bug in error printing which mispositions error indicators when near code with tabs. The code attempted to fix the issue by replacing spaces with tabs, but it sadly wasn't enough, as sometimes you may not print spaces but _ or ^ instead. This patch employs the reverse strategy: it replaces each tab with a space, so that the number of _ and ^ and spaces in error indicators below the code snippet line up perfectly. In a study [1] preceeding this patch, we could see that this strategy is also chosen by gcc version 6.3.0. Its not perfect, as the output is not beautiful, but its the easiest to implement. If anyone wants to improve on this, be my guest! This patch is meant as improvement of the status quo, not as perfect end status. It fixes the actual issue of mispositioning error indicators. [1]: https://github.com/rust-lang/rust/issues/38384#issuecomment-326813710
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-24 01:19:28 +0000