| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-08-21 | Add terminal_width debugging flag | Esteban Küber | -1/+1 | |
| 2019-07-28 | Remove lint annotations in specific crates that are already enforced by ↵ | Vadim Petrochenkov | -1/+0 | |
| rustbuild Remove some random unnecessary lint `allow`s | ||||
| 2019-07-11 | syntax: Make def-site span mandatory in ↵ | Vadim Petrochenkov | -5/+4 | |
| ExpnInfo/MacroBacktrace/DiagnosticSpanMacroExpansion We have to deal with dummy spans anyway Remove def-site span from expander interfaces. It's not used by the expansion infra, only by specific expanders, which can keep it themselves if they want it. | ||||
| 2019-05-21 | Make -Zemit-artifact-notifications also emit the artifact type | Jeremy Fitzhardinge | -2/+4 | |
| This is easier for tooling to handle than trying to reverse-engineer it from the filename extension. | ||||
| 2019-05-07 | rustc: rename -Z emit-directives to -Z emit-artifact-notifications and ↵ | Eduard-Mihai Burtescu | -6/+7 | |
| simplify the output. | ||||
| 2019-04-30 | In JSON output, emit a directive after metadata is generated. | Nicholas Nethercote | -2/+20 | |
| To implement pipelining, Cargo needs to know when metadata generation is finished. This commit adds code to do that. Unfortunately, metadata file writing currently occurs very late during compilation, so pipelining won't produce a speed-up. Moving metadata file writing earlier will be a follow-up. The change involves splitting the existing `Emitter::emit` method in two: `Emitter::emit_diagnostic` and `Emitter::emit_directive`. The JSON directives look like this: ``` {"directive":"metadata file written: liba.rmeta"} ``` The functionality is behind the `-Z emit-directives` option, and also requires `--error-format=json`. | ||||
| 2019-04-17 | Rollup merge of #59128 - oli-obk:colorful_json, r=mark-i-m,eddyb | Mazdak Farrokhzad | -11/+20 | |
| Emit ansi color codes in the `rendered` field of json diagnostics cc @ljedrz Implemented for https://github.com/rust-lang/rust/pull/56595#issuecomment-447645115 (x.py clippy) | ||||
| 2019-04-10 | Tweak unstable diagnostic output | Esteban Küber | -13/+11 | |
| 2019-04-02 | Rename `colorful-json` to `json-rendered` and make it a selection instead of ↵ | Oliver Scherer | -9/+9 | |
| a bool | ||||
| 2019-04-02 | Emit ansi color codes in the `rendered` field of json diagnostics | Oliver Scherer | -10/+19 | |
| 2019-02-13 | Rollup merge of #58273 - taiki-e:rename-dependency, r=matthewjasper | Mazdak Farrokhzad | -5/+6 | |
| Rename rustc_errors dependency in rust 2018 crates I think this is a better solution than `use rustc_errors as errors` in `lib.rs` and `use crate::errors` in modules. Related: rust-lang/cargo#5653 cc #58099 r? @Centril | ||||
| 2019-02-13 | Cleanup imports | Taiki Endo | -1/+2 | |
| 2019-02-13 | Rename rustc_errors dependency in rust 2018 crates | Taiki Endo | -4/+4 | |
| 2019-02-10 | rustc: doc comments | Alexander Regueiro | -1/+1 | |
| 2019-02-07 | libsyntax => 2018 | Taiki Endo | -8/+8 | |
| 2019-01-13 | Cosmetic improvements | Alexander Regueiro | -1/+1 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-10-29 | Rename other occs of (Code/File)Map to Source(Map/File) #51574 | David Lavati | -9/+9 | |
| 2018-08-19 | mv (mod) codemap source_map | Donato Sciarra | -1/+1 | |
| 2018-08-19 | mv filemap source_file | Donato Sciarra | -2/+2 | |
| 2018-08-19 | mv FileMap SourceFile | Donato Sciarra | -1/+1 | |
| 2018-08-19 | mv CodeMap SourceMap | Donato Sciarra | -6/+6 | |
| 2018-07-10 | Deny bare trait objects in in src/libsyntax | ljedrz | -3/+3 | |
| 2018-05-21 | Stabilize suggestion applicability field in json output | Manish Goregaokar | -17/+4 | |
| 2018-04-25 | Approximate -> Applicability | Manish Goregaokar | -13/+13 | |
| 2018-04-24 | Use enum for approximate suggestions | Manish Goregaokar | -5/+5 | |
| 2018-03-15 | Require the code mapper to be thread-safe | John Kåre Alsaker | -2/+2 | |
| 2018-03-02 | Replace Rc with Lrc for shared data | John Kåre Alsaker | -5/+5 | |
| 2018-02-26 | Support flag `-Z ui-testing` for tweaking diagnostic output for UI tests | Vadim Petrochenkov | -1/+9 | |
| 2018-02-01 | Auto merge of #47540 - Manishearth:suggestion, r=nrc | bors | -10/+30 | |
| Add approximate suggestions for rustfix This adds `span_approximate_suggestion()` that lets you emit a suggestion marked as "non-machine applicable" in the JSON output. UI users see no difference. This is for when rustc and clippy wish to emit suggestions which will make sense to the reader (e.g. they may have placeholders like `<type>`) but are not source-applicable, so that rustfix/etc can ignore these. fixes #39254 | ||||
| 2018-01-29 | Toggle span highlighting on `-Zteach` | Esteban Küber | -1/+1 | |
| 2018-01-29 | Add internal-only rustc_serialize_exclude_null attribute for making the ↵ | Manish Goregaokar | -0/+2 | |
| field only exist in the json if the flag is passed | ||||
| 2018-01-29 | Add -Zapproximate-suggestions | Manish Goregaokar | -4/+18 | |
| 2018-01-29 | Add approximate suggestions for rustfix | Manish Goregaokar | -7/+11 | |
| This adds `span_approximate_suggestion()` that lets you emit a suggestion marked as "approximate" in the JSON output. UI users see no difference. This is for when rustc and clippy wish to emit suggestions which will make sense to the reader (e.g. they may have placeholders like `<type>`) but are not source-applicable, so that rustfix/etc can ignore these. fixes #39254 | ||||
| 2017-12-14 | Use PathBuf instead of String where applicable | Oliver Schneider | -1/+1 | |
| 2017-11-20 | Address PR comments | Oliver Schneider | -1/+1 | |
| 2017-11-20 | Include rendered diagnostic in json | Oliver Schneider | -3/+25 | |
| 2017-11-16 | Remove left over dead code from suggestion diagnostic refactoring | Oliver Schneider | -12/+2 | |
| 2017-11-09 | Auto merge of #45741 - oli-obk:refactor_suggestions, r=estebank | bors | -4/+4 | |
| Refactor internal suggestion API ~~The only functional change is that whitespace, which is suggested to be added, also gets `^^^^` under it. An example is shown in the tests (the only test that changed).~~ Continuation of #41876 r? @nagisa the changes are probably best viewed [without whitespace](https://github.com/rust-lang/rust/pull/45741/files?w=1) | ||||
| 2017-11-03 | Refactor internal suggestion API | Oliver Schneider | -4/+4 | |
| 2017-11-03 | Pretty print json in ui tests | Oliver Schneider | -6/+16 | |
| 2017-11-03 | Remove outdated documentation | Oliver Schneider | -6/+2 | |
| 2017-11-02 | Make the difference between lint codes and error codes explicit | Oliver Schneider | -2/+6 | |
| 2017-10-24 | Reduce the repetition in json error output | Oliver Schneider | -17/+9 | |
| 2017-08-30 | Make fields of `Span` private | Vadim Petrochenkov | -4/+4 | |
| 2017-08-17 | Rollup merge of #43891 - Fourchaux:master, r=steveklabnik | Corey Farwell | -1/+1 | |
| Fix typos & us spellings Fixing some typos and non en-US spellings. (Update of PR https://github.com/rust-lang/rust/pull/42812 ) | ||||
| 2017-08-15 | use field init shorthand EVERYWHERE | Zack M. Davis | -7/+7 | |
| Like #43008 (f668999), but _much more aggressive_. | ||||
| 2017-08-15 | Fix typos & us spellings | Fourchaux | -1/+1 | |
| 2017-07-21 | make JSON error byte position start at top of file | Zack M. Davis | -3/+2 | |
| The `hi` and `lo` offsets in a span are relative to a `CodeMap`, but this doesn't seem to be terribly useful for tool consumers who don't have the codemap, but might want the byte offset within an actual file? Resolves #35164. | ||||
| 2017-07-06 | Only underline suggestion if it is not the only code being shown | Esteban Küber | -1/+1 | |
