https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.73.0 2023-07-31T07:19:23+00:00 2023-07-31T07:19:23+00:00 Oli Scherer git-spam-no-reply9815368754983@oli-obk.de 2023-07-25T13:09:53+00:00 urn:sha1:29de70da1be1c71b89b006f9955fedc70e084067 2023-07-03T20:04:18+00:00 Trevor Gross tmgross@umich.edu 2022-12-19T18:09:40+00:00 urn:sha1:6a1c10bd85442f52f1d55d51005481cfa5cb40b5 Currently, the output of `rustc --explain foo` displays the raw markdown in a pager. This is acceptable, but using actual formatting makes it easier to understand. This patch consists of three major components: 1. A markdown parser. This is an extremely simple non-backtracking recursive implementation that requires normalization of the final token stream 2. A utility to write the token stream to an output buffer 3. Configuration within rustc_driver_impl to invoke this combination for `--explain`. Like the current implementation, it first attempts to print to a pager with a fallback colorized terminal, and standard print as a last resort. If color is disabled, or if the output does not support it, or if printing with color fails, it will write the raw markdown (which matches current behavior). Pagers known to support color are: `less` (with `-r`), `bat` (aka `catbat`), and `delta`. The markdown parser does not support the entire markdown specification, but should support the following with reasonable accuracy: - Headings, including formatting - Comments - Code, inline and fenced block (no indented block) - Strong, emphasis, and strikethrough formatted text - Links, anchor, inline, and reference-style - Horizontal rules - Unordered and ordered list items, including formatting This parser and writer should be reusable by other systems if ever needed. 2023-05-09T15:20:13+00:00 klensy klensy@users.noreply.github.com 2023-05-09T15:20:13+00:00 urn:sha1:3c03cce341ef9be288f05e0be3e9fe56100d37ba 2023-04-18T18:56:22+00:00 Nilstrieb 48135649+Nilstrieb@users.noreply.github.com 2023-04-16T12:33:00+00:00 urn:sha1:b5d3d970fa64c25eecfbd8ebbae601a2c6cb2cb3 Fluent, with all the icu4x it brings in, takes quite some time to compile. `fluent_messages!` is only needed in further downstream rustc crates, but is blocking more upstream crates like `rustc_index`. By splitting it out, we allow `rustc_macros` to be compiled earlier, which speeds up `x check compiler` by about 5 seconds (and even more after the needless dependency on `serde_json` is removed from `rustc_data_structures`). 2023-03-20T17:19:35+00:00 Andy Russell arussell123@gmail.com 2023-01-15T18:43:15+00:00 urn:sha1:bb7c373fdf6c7c3fb8e204dcc178d870644fcc4b 2022-12-28T01:59:21+00:00 Jhonny Bill Mena jhonnybillm@gmail.com 2022-11-17T13:53:14+00:00 urn:sha1:d1030fab229d25d3ca14b1aaa2fc8e5a6ec932a8 2022-11-19T14:35:18+00:00 Matthias Krüger matthias.krueger@famsik.de 2022-11-19T14:35:18+00:00 urn:sha1:52cc0d5360622fe505b4f25973e06b1c9600f07c Use `IsTerminal` in place of `atty` In any crate that can use nightly features, use `IsTerminal` rather than `atty`: - Use `IsTerminal` in `rustc_errors` - Use `IsTerminal` in `rustc_driver` - Use `IsTerminal` in `rustc_log` - Use `IsTerminal` in `librustdoc` 2022-11-18T22:46:35+00:00 Charles Lew crlf0710@gmail.com 2022-11-06T17:25:48+00:00 urn:sha1:d15b020278fc97ec978af94159e5b0f70e14c6ed 2022-10-16T14:10:40+00:00 Josh Triplett josh@joshtriplett.org 2022-10-16T13:53:21+00:00 urn:sha1:c5ad97da258bb47cba2f888cee73b0f4b5289d58 2022-09-29T07:49:04+00:00 reez12g reez12g@gmail.com 2022-09-11T07:04:02+00:00 urn:sha1:9a4c5abe453329d4b492e33b442b36011a632117