| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-12-18 | Switch compiler/ to intra-doc links | Joshua Nelson | -2/+0 | |
| rustc_lint and rustc_lint_defs weren't switched because they're included in the compiler book and so can't use intra-doc links. | ||||
| 2020-12-16 | Fix typo in method name | Camelid | -2/+2 | |
| unsuccessfull -> unsuccessful | ||||
| 2020-12-16 | Add more documentation to `Diagnostic` and `DiagnosticBuilder` | Camelid | -11/+50 | |
| 2020-11-17 | Rollup merge of #74293 - GuillaumeGomez:rustdoc-test-compiler-output-color, ↵ | Mara Bos | -0/+17 | |
| r=jyn514 Rustdoc test compiler output color Fixes #72915 We just need to be sure it doesn't break rustdoc doctests' compilation checks. Maybe some other unforeseen consequences too? r? `@ehuss` cc `@rust-lang/rustdoc` | ||||
| 2020-11-17 | Simplfy color availability check | Guillaume Gomez | -0/+17 | |
| 2020-11-16 | clarify `span_label` documentation | Andy Russell | -8/+10 | |
| 2020-11-03 | Auto merge of #76931 - oli-obk:const_prop_inline_lint_madness, r=wesleywiser | bors | -2/+5 | |
| Properly handle lint spans after MIR inlining The first commit shows what happens when we apply mir inlining and then cause lints on the inlined MIR. The second commit fixes that. r? `@wesleywiser` | ||||
| 2020-10-30 | Some work | Aaron Hill | -2/+8 | |
| 2020-10-30 | Implement rustc side of report-future-incompat | Aaron Hill | -39/+136 | |
| 2020-10-30 | Fix even more clippy warnings | Joshua Nelson | -16/+4 | |
| 2020-10-29 | Fix typos | Dániel Buga | -2/+2 | |
| 2020-10-27 | Address review comment | oli | -1/+2 | |
| 2020-10-27 | Show the inline stack of MIR lints that only occur after inlining | Oliver Scherer | -2/+4 | |
| 2020-10-14 | Remove unused code from remaining compiler crates | est31 | -15/+0 | |
| 2020-09-23 | /nightly/nightly-rustc | Erik Hofmayer | -1/+1 | |
| 2020-09-23 | Updated html_root_url for compiler crates | Erik Hofmayer | -1/+1 | |
| 2020-09-21 | Rollup merge of #76846 - botika:master, r=davidtwco | Ralf Jung | -21/+13 | |
| Avoiding unnecesary allocations at rustc_errors Simplify the code avoiding allocations with easy alternative | ||||
| 2020-09-18 | use matches!() macro for simple if let conditions | Matthias Krüger | -5/+3 | |
| 2020-09-18 | Simplify panic_if_treat_err_as_bug avoiding allocations | Juan Aguilar Santillana | -7/+5 | |
| 2020-09-17 | Remove redundant to_string | Juan Aguilar Santillana | -14/+8 | |
| 2020-09-11 | replacing sub's that can wrap by saturating_sub's | Aurélien Deharbe | -3/+3 | |
| 2020-09-02 | rustc_{errors,session}: add `delay_good_path_bug` | Dan Aloni | -7/+48 | |
| The first use case of this detection of regression for trimmed paths computation, that is in the case of rustc, which should be computed only in case of errors or warnings. Our current user of this method is deeply nested, being a side effect from `Display` formatting on lots of rustc types. So taking only the caller to the error message is not enough - we should collect the traceback instead. | ||||
| 2020-08-30 | mv compiler to compiler/ | mark | -0/+5529 | |
