| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2021-08-16 | Use note to point at bound introducing requirement | Esteban Küber | -4/+4 | |
| 2021-08-09 | Link to edition guide instead of issues for 2021 lints. | Mara Bos | -2/+2 | |
| 2021-08-04 | Remove trailing whitespace from error messages | Fabian Wolff | -1/+1 | |
| 2021-07-19 | Various diagnostics clean ups/tweaks | Esteban Küber | -13/+101 | |
| * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition | ||||
| 2021-06-25 | Address PR feedback | Ryan Levick | -5/+5 | |
| 2021-06-25 | Change how edition based future compatibility warnings are handled | Ryan Levick | -5/+5 | |
| 2021-05-12 | Show macro name in 'this error originates in macro' message | Aaron Hill | -15/+15 | |
| When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. | ||||
| 2021-04-16 | Fix tests | Ryan Levick | -4/+11 | |
| 2021-04-08 | Update BARE_TRAIT_OBJECT and ELLIPSIS_INCLUSIVE_RANGE_PATTERNS to errors in ↵ | Ryan Levick | -0/+41 | |
| Rust 2021 | ||||
| 2021-02-09 | ./x.py test --bless | Tomasz Miąsko | -275/+11 | |
| 2021-01-13 | Update code to account for extern ABI requirement | Mark Rousskov | -1/+1 | |
| 2020-10-06 | Fix tests from rebase | Matthew Jasper | -1/+3 | |
| 2020-10-06 | Separate bounds and predicates for associated/opaque types | Matthew Jasper | -1/+1 | |
| 2020-09-02 | pretty: trim paths of unique symbols | Dan Aloni | -90/+90 | |
| 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-08-27 | Abort when catch_unwind catches a foreign exception | Amanieu d'Antras | -6/+9 | |
| 2020-08-16 | hir: simplify `is_range_literal` | David Wood | -1/+5 | |
| This commit simplifies `is_range_literal` by checking for `QPath::LangItem` containing range-related lang items, rather than using a heuristic. Co-authored-by: Matthew Jasper <mjjasper1@gmail.com> Signed-off-by: David Wood <david@davidtw.co> | ||||
| 2020-07-14 | Remove `Sized` `on_unimplemented` note | Esteban Küber | -1/+0 | |
| 2020-07-02 | Audit uses of `span_suggestion_short` | Yuki Okushi | -32/+65 | |
| 2020-06-22 | Change heuristic for determining range literal | Ayaz Hafiz | -0/+43 | |
| Currently, rustc uses a heuristic to determine if a range expression is not a literal based on whether the expression looks like a function call or struct initialization. This fails for range literals whose lower/upper bounds are the results of function calls. A possibly-better heuristic is to check if the expression contains `..`, required in range literals. Of course, this is also not perfect; for example, if the range expression is a struct which includes some text with `..` this will fail, but in general I believe it is a better heuristic. A better alternative altogether is to add the `QPath::LangItem` enum variant suggested in #60607. I would be happy to do this as a precursor to this patch if someone is able to provide general suggestions on how usages of `QPath` need to be changed later in the compiler with the `LangItem` variant. Closes #73553 | ||||
| 2020-04-11 | rustc: Add a warning count upon completion | RoccoDev | -1/+1 | |
| 2020-03-05 | Remove eh_unwind_resume lang item | Amanieu d'Antras | -10/+6 | |
| 2020-02-06 | rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. | Eduard-Mihai Burtescu | -0/+42 | |
| 2020-01-24 | Normalise notes with the/is | varkor | -1/+1 | |
| 2020-01-09 | Update tests | Vadim Petrochenkov | -11/+251 | |
| 2019-11-18 | Surround types with backticks in type errors | Esteban Küber | -1/+1 | |
| 2019-11-18 | Specific labels when referring to "expected" and "found" types | Esteban Küber | -48/+48 | |
| 2019-07-03 | Migrate compile-pass annotations to build-pass | Yuki Okushi | -3/+3 | |
| 2019-04-22 | Remove double trailing newlines | varkor | -6/+0 | |
| 2019-04-18 | hide `--explain` hint if error has no extended info | Andy Russell | -1/+1 | |
| 2019-03-11 | Update tests | Vadim Petrochenkov | -3/+3 | |
| 2019-01-01 | Fix broken links to second edition TRPL. | Corey Farwell | -1/+1 | |
| Fixes https://github.com/rust-lang/rust/issues/57104. | ||||
| 2018-12-25 | Remove licenses | Mark Rousskov | -113/+23 | |
| 2018-11-15 | Rollup merge of #55852 - varkor:dotdotequals-lint, r=zackmdavis | Pietro Albini | -2/+2 | |
| Rewrite `...` as `..=` as a `MachineApplicable` 2018 idiom lint Fixes https://github.com/rust-lang/rust/issues/51043. | ||||
| 2018-11-10 | Use non-short suggestion for parenthesised ..= | varkor | -1/+1 | |
| 2018-11-10 | Rewrite `...` as `..=` as a MachineApplicable 2018 idiom lint | varkor | -2/+2 | |
| 2018-11-10 | Auto merge of #55626 - nikic:update-emscripten, r=alexcrichton | bors | -1/+1 | |
| Update emscripten This updates emscripten to 1.38.15, which is based on LLVM 6.0.1 and would allow us to drop code for handling LLVM 4. The main issue I ran into is that exporting statics through `EXPORTED_FUNCTIONS` no longer works. As far as I understand exporting non-functions doesn't really make sense under emscripten anyway, so I've modified the symbol export code to not even try. Closes #52323. | ||||
| 2018-11-08 | Fix some tests for wasm32-unknown-emscripten | Nikita Popov | -1/+1 | |
| 2018-11-07 | Removed `#[rustc_error]` from tests that are all `// compile-pass`. | Felix S. Klock II | -33/+9 | |
| 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-10-09 | Fix test for windows os | Paweł Romanowski | -6/+10 | |
| 2018-10-08 | Attempt to fix #54505 tests for wasm | Paweł Romanowski | -11/+12 | |
| 2018-10-02 | Address review comments | Paweł Romanowski | -74/+24 | |
| 2018-10-02 | Fix range borrowing suggestions logic | Paweł Romanowski | -3/+313 | |
| 2018-09-29 | First stab at fixing #54505 | Paweł Romanowski | -0/+327 | |
| 2018-08-14 | Merged migrated compile-fail tests and ui tests. Fixes #46841. | David Wood | -0/+438 | |
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |