Repository navigation
Output remapped paths in rustdoc JSON with the documentation scope - #164278
Conversation
|
These commits modify Please ensure that if you've changed the output:
cc @obi1kenobi |
5b2e639 to
835129f
Compare
DOCUMENTATION scopedocumentation scope
835129f to
f8d4856
Compare
43fbba2 to
1efec5a
Compare
1efec5a to
0d0f404
Compare
|
Thanks! @bors r+ rollup |
|
Out of curiosity, is this worth bumping the format version, or not? I have no opinion one way or the other, I'm just curious since I'm not sure about the implications of this PR. E.g., whether any behaviors would visibly change to existing consumers, including |
…uillaumeGomez Output remapped paths in rustdoc JSON with the `documentation` scope Let's make rustdoc-json respect `--remap-path-prefix` and `--remap-path-scope` (if passed), by using the `documentation` scope. That's a perfect application for the rustdoc-only `documentation` scope.
I don't think so, the format it-self doesn't change. The only thing that changes is the value of Quickly looking at |
|
One thing may see however is that for the distributed standard library json |
Rollup of 9 pull requests Successful merges: - #162749 (Recover missing `turbofish` for `lifetime` arguments in expression position) - #164170 (Prefer WriteConsoleW for stdout on Windows) - #164255 (test DSL eagerly handle false constraints) - #163230 (Document zero-sized allocations properly for `Box` and `Vec`) - #163940 (Parse move exprs as a bottom expr instead of a prefix expr) - #164219 (Windows FileExt trait doesn't need to handle ErrorKind::Interrupted; test improvements for same) - #164220 (Test the interaction between `--remap-path-prefix` and doctests) - #164266 (rustdoc: Improvements for `rustc_must_implement_one_of`) - #164278 (Output remapped paths in rustdoc JSON with the `documentation` scope)
|
💔 I suspect this PR failed tests as part of a rollup After fixing the problem, consider running a try job for the failed job before re-approving. Link to failure: #164296 (comment) |
|
This pull request was unapproved. This PR was contained in a rollup (#164296), which was unapproved. |
|
@bors try jobs=aarch64,test-various |
This comment has been minimized.
This comment has been minimized.
Output remapped paths in rustdoc JSON with the `documentation` scope try-job: *aarch64* try-job: test-various
4117a5e to
7fec32e
Compare
|
@bors try jobs=aarch64,test-various |
This comment has been minimized.
This comment has been minimized.
Output remapped paths in rustdoc JSON with the `documentation` scope try-job: *aarch64* try-job: test-various
|
@bors r=GuillaumeGomez |
…uillaumeGomez Output remapped paths in rustdoc JSON with the `documentation` scope Let's make rustdoc-json respect `--remap-path-prefix` and `--remap-path-scope` (if passed), by using the `documentation` scope. That's a perfect application for the rustdoc-only `documentation` scope.
Rollup of 7 pull requests Successful merges: - #163132 (Test panics and wasm32-wasip3 in CI, not wasip1) - #164076 (Fix ICE when move expressions reference out-of-scope local bindings) - #162432 (Improve diagnostics for non-well-formed associated items) - #164138 (cg_llvm: Use a callback to enforce scoped lifetimes in ModuleLlvm ) - #164220 (Test the interaction between `--remap-path-prefix` and doctests) - #164225 (Point at assoc item for trait that needs to be implemented) - #164278 (Output remapped paths in rustdoc JSON with the `documentation` scope)
…uwer Rollup of 14 pull requests Successful merges: - #163132 (Test panics and wasm32-wasip3 in CI, not wasip1) - #164314 (Abby: use a smallvec for `And`/`Or` constraints) - #148413 (Mangle personality symbol) - #163688 (Add aarch64-unknown-qtee as a tier 3 target) - #164076 (Fix ICE when move expressions reference out-of-scope local bindings) - #164327 ([coff] Symbol renaming stored the original name, not the undecorated name) - #162432 (Improve diagnostics for non-well-formed associated items) - #164138 (cg_llvm: Use a callback to enforce scoped lifetimes in ModuleLlvm ) - #164210 (`incomplete` -> `unstable` for delegation feature) - #164225 (Point at assoc item for trait that needs to be implemented) - #164278 (Output remapped paths in rustdoc JSON with the `documentation` scope) - #164308 (format abby dsl errors better) - #164335 (expand and document tool attribute shadowing test) - #164342 (Use regular type parsing for argument-position const parameters)
Rollup merge of #164278 - Urgau:rustdoc-json-remap-path, r=GuillaumeGomez Output remapped paths in rustdoc JSON with the `documentation` scope Let's make rustdoc-json respect `--remap-path-prefix` and `--remap-path-scope` (if passed), by using the `documentation` scope. That's a perfect application for the rustdoc-only `documentation` scope.
…cope-of-object, r=GuillaumeGomez Make the `documentation` scope a sub-scope of the `object` scope ~~First commit from rust-lang#164278.~~ This PR moves the `documentation` scope to be a sub-scope of the `object` scope. The `object` scope is currently defined to be: "This ensures all paths in compiled executables, libraries and objects outputs are remapped but not elsewhere", which can be translated to mean everything written to disk by `rustc` it-self. It is therefore a natural extension for the `documentation` scope to be a sub-scope of it, like `macro`, `debuginfo` and `coverage`, since we use it for things written down on disk, like rustdoc-json (with rust-lang#164278 at-least) or the source code viewer.
…cope-of-object, r=GuillaumeGomez Make the `documentation` scope a sub-scope of the `object` scope ~~First commit from rust-lang#164278.~~ This PR moves the `documentation` scope to be a sub-scope of the `object` scope. The `object` scope is currently defined to be: "This ensures all paths in compiled executables, libraries and objects outputs are remapped but not elsewhere", which can be translated to mean everything written to disk by `rustc` it-self. It is therefore a natural extension for the `documentation` scope to be a sub-scope of it, like `macro`, `debuginfo` and `coverage`, since we use it for things written down on disk, like rustdoc-json (with rust-lang#164278 at-least) or the source code viewer.
|
Note This PR was benchmarked as part of triage of its containing rollup: triage URL. Finished benchmarking commit (0189fb4): comparison URL. Overall result: ❌ regressions - please read:Our benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary -4.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (secondary -1.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Artifact size: 407.05 MiB -> 407.16 MiB (0.03%) |
…cope-of-object, r=GuillaumeGomez Make the `documentation` scope a sub-scope of the `object` scope ~~First commit from rust-lang#164278.~~ This PR moves the `documentation` scope to be a sub-scope of the `object` scope. The `object` scope is currently defined to be: "This ensures all paths in compiled executables, libraries and objects outputs are remapped but not elsewhere", which can be translated to mean everything written to disk by `rustc` it-self. It is therefore a natural extension for the `documentation` scope to be a sub-scope of it, like `macro`, `debuginfo` and `coverage`, since we use it for things written down on disk, like rustdoc-json (with rust-lang#164278 at-least) or the source code viewer.
Rollup merge of #164279 - Urgau:documentation-scope-as-sub-scope-of-object, r=GuillaumeGomez Make the `documentation` scope a sub-scope of the `object` scope ~~First commit from #164278.~~ This PR moves the `documentation` scope to be a sub-scope of the `object` scope. The `object` scope is currently defined to be: "This ensures all paths in compiled executables, libraries and objects outputs are remapped but not elsewhere", which can be translated to mean everything written to disk by `rustc` it-self. It is therefore a natural extension for the `documentation` scope to be a sub-scope of it, like `macro`, `debuginfo` and `coverage`, since we use it for things written down on disk, like rustdoc-json (with #164278 at-least) or the source code viewer.
View all comments
Let's make rustdoc-json respect
--remap-path-prefixand--remap-path-scope(if passed), by using thedocumentationscope.That's a perfect application for the rustdoc-only
documentationscope.r? @GuillaumeGomez