diff options
| author | bors <bors@rust-lang.org> | 2022-09-19 02:13:54 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-09-19 02:13:54 +0000 |
| commit | c8e12cc8bf0de646234524924f39c85d9f3c7c37 (patch) | |
| tree | 8171778babc259edafa48ae8332e304b569f06c5 /src/librustdoc/html/static/js/source-script.js | |
| parent | a37499ae66ec5fc52a93d71493b78fb141c32f6b (diff) | |
| parent | 235dccef2b8012e7d9da87f4b6091912d802cff2 (diff) | |
| download | rust-c8e12cc8bf0de646234524924f39c85d9f3c7c37.tar.gz rust-c8e12cc8bf0de646234524924f39c85d9f3c7c37.zip | |
Auto merge of #101799 - LukeMathWalker:distribute-json-doc, r=jyn514
Distribute json doc # Overview We add a new component, `rust-json-docs`, to distribute the JSON version of rustdoc's output for public compiler crates (i.e. `std`, `alloc`, `proc_macro`, `core` and `test`). As discussed in #101383, we do not bundle this up as part of the existing `rust-docs` component since `rustdoc`'s JSON format is still unstable. # Open questions / Doubts I tried my best, but I never touched this codebase and I couldn't find much documentation on how `dist` works - I pattern-matched existing code, which might have led to some non-sensical choices in the eyes of people more familiar with the codebase. In particular, I am not sure if my choice of adding a new config flag is appropriate or if the decision to build/not build the JSON docs is more appropriately gated by one of the existing flags. Any suggestion is more than welcome. Closes #101383
Diffstat (limited to 'src/librustdoc/html/static/js/source-script.js')
0 files changed, 0 insertions, 0 deletions