https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.56.0 2021-04-17T16:21:52+00:00 2021-04-17T16:21:52+00:00 Michael Howell michael@notriddle.com 2021-03-17T18:41:01+00:00 urn:sha1:6516f9408ef47137e070c2635b9f4a67d848f129 Instead of using a depth counter and adding "../" to get to the top, this commit makes rustdoc actually compare the path of what it's linking from to the path that it's linking to. This makes the resulting HTML shorter. Here's a comparison of one of the largest (non-source) files in the Rust standard library docs (about 4% improvement before gzipping). $ wc -c struct.Wrapping.old.html struct.Wrapping.new.html 2387389 struct.Wrapping.old.html 2298538 struct.Wrapping.new.html Most if it can be efficiently gzipped away. $ wc -c struct.Wrapping.old.html.gz struct.Wrapping.new.html.gz 70679 struct.Wrapping.old.html.gz 70050 struct.Wrapping.new.html.gz But it also makes a difference in the final DOM size, reducing it from 91MiB to 82MiB. 2019-08-24T17:11:57+00:00 Aaron Hill aa1ronham@gmail.com 2019-07-20T20:34:41+00:00 urn:sha1:14986081355db0a2ae67df6a43dd9e6e360d718c Fixes #58700 Fixes #58696 Fixes #49553 Fixes #52210 This commit removes the special rustdoc handling for proc macros, as we can now retrieve their span and attributes just like any other item. A new command-line option is added to rustdoc: `--crate-type`. This takes the same options as rustc's `--crate-type` option. However, all values other than `proc-macro` are treated the same. This allows Rustdoc to enable 'proc macro mode' when handling a proc macro crate. In compiletest, a new 'rustdoc-flags' option is added. This allows us to pass in the '--proc-macro-crate' flag in the absence of Cargo. I've opened [an additional PR to Cargo](https://github.com/rust-lang/cargo/pull/7159) to support passing in this flag. These two PRS can be merged in any order - the Cargo changes will not take effect until the 'cargo' submodule is updated in this repository. 2019-07-10T21:12:07+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2019-06-18T19:23:13+00:00 urn:sha1:48635226d8d71f18b09ea40f5cdbe34dbaaf378f It's internal to resolve and always results in `Res::Err` outside of resolve. Instead put `DefKind::Fn`s themselves into the macro namespace, it's ok. Proc macro stubs are items placed into macro namespase for functions that define proc macros. https://github.com/rust-lang/rust/pull/52383 The rustdoc test is changed because the old test didn't actually reproduce the ICE it was supposed to reproduce. 2019-01-22T21:44:19+00:00 QuietMisdreavus grey@quietmisdreavus.net 2019-01-22T21:44:19+00:00 urn:sha1:b876694734cfc5919b8c12527c287aea1a8d8cfd 2018-12-26T04:08:33+00:00 Mark Rousskov mark.simulacrum@gmail.com 2018-12-25T15:56:47+00:00 urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718c 2018-12-08T18:33:09+00:00 Oliver Middleton olliemail27@gmail.com 2018-12-08T18:27:12+00:00 urn:sha1:0bb075f5a512affd6f5bb6a573e8b0188e6c0132 Filter out `ProcMacroStub`s to avoid an ICE during cleaning. Also add proc macros to `cache().paths` so it can generate links. 2018-11-30T04:15:20+00:00 Eduard-Mihai Burtescu edy.burt@gmail.com 2018-11-24T13:34:13+00:00 urn:sha1:3369929ddb7a3be8048636ed376d05f1a3295378 2018-11-30T04:15:20+00:00 Eduard-Mihai Burtescu edy.burt@gmail.com 2018-03-20T18:20:03+00:00 urn:sha1:d3ab4a74efad266155fcd402c8d159af9e443e3d 2018-09-27T15:22:29+00:00 QuietMisdreavus grey@quietmisdreavus.net 2018-09-27T15:22:29+00:00 urn:sha1:d37f3696b167251a96b8f0e4b33336d023daa2c5 2018-09-25T19:56:43+00:00 QuietMisdreavus grey@quietmisdreavus.net 2018-09-25T19:56:43+00:00 urn:sha1:aea1bd0a5908430d41b6f2d38240f2652ef5651f