| Age | Commit message (Collapse) | Author | Lines |
|---|
|
r=aDotInTheVoid
Made `Path::name` only have item name rather than full name
Closes #134853
This PR makes `Path::name` to only have item name rather than full name, i.e. with the following code
```rust
pub mod foo {
pub struct Bar;
}
pub fn get_bar() -> foo::Bar {
foo::Bar
}
```
and running `./rustdoc ./demo.rs -wjson -Zunstable-options` gives:
```json
{
"41": {
"id": 41,
"name": "get_bar",
"inner": {
"function": {
"sig": {
"inputs": [],
"output": {
"resolved_path": {
"name": "Bar",
"id": 0,
"args": { "angle_bracketed": { "args": [], "constraints": [] }
}
}
}
}
}
}
}
}
```
_Information which isn't useful here was trimmed_
r? aDotInTheVoid
|
|
Enable "jump to def" feature on patterns
Part of https://github.com/rust-lang/rust/issues/89095.
Pattern (as in "patterns in pattern matching") were not handled by the feature, it's now added.
It all started when I realized that prelude values like `Some` or `Err` were not getting a link generated either (added support for it in the first commit).
r? ``@fmease``
|
|
|
|
Co-authored-by: binarycat <binarycat@envs.net>
|
|
rustc_allowed_through_unstable_modules to more items
|
|
|
|
|
|
|
|
r=GuillaumeGomez
Subtree update cg_gcc 2025/01/12
r? GuillaumeGomez
|
|
|
|
|
|
See: https://github.com/rust-lang/rust/issues/131467#issuecomment-2529314603.
|
|
|
|
|
|
Use deref_poiner_as instead of deref_pointer
|
|
|
|
|
|
|
|
use a single large catch_unwind in lang_start
I originally planned to use `abort_unwind` but reading the comment in `thread_cleanup` it seems we are deliberately going for slightly nicer error messages here, so this preserves that. It still seems nice to not repeat `catch_unwind` so often.
|
|
bootstrap: fix outdated feature name in comment
Follow-up to https://github.com/rust-lang/rust/pull/135391#discussion_r1912826594.
I guess I updated everything else **except** the comment right next to the actual dependencies 💀
r? bootstrap
|
|
|
|
|
|
|
|
|
|
|
|
A clone-like function in a function that takes as an argument the type
that it returns.
However, functions that return a type variable are not counted as
clone-line. Because we're not unifying the whole function at once,
a function like `U -> T` would otherwise be counted as "clone-like"
because the generics will just unify with anything when done seperatly.
Co-authored-by: Michael Howell <michael@notriddle.com>
|
|
It has been a bit of a pain trying to keep the lints in sync across
the submodule repositories, so the just turns it off.
|
|
|
|
This time without missing bindings.
Solve it by returning to the old ways, i.e. just throw the extra nodes away.
In other words, I acknowledge defeat.
|
|
Enable optimised AArch64 dist builds with the opt-dist pipeline.
For the time being, disable bolt on aarch64 due to upstream bolt bugs.
|
|
The new code is more explicit and avoids trait magic that added needless
complexity to this part of rustdoc.
|
|
Rollup of 3 pull requests
Successful merges:
- #135355 (ci: added test log format for ci)
- #135386 (clean up code related to the rustdoc-js test suite)
- #135391 (bootstrap: Implement conditional `tracing` infra)
r? `@ghost`
`@rustbot` modify labels: rollup
|
|
bootstrap: Implement conditional `tracing` infra
Add a conditional `tracing` setup that is gated behind `BOOTSTRAP_TRACING` env var. This `tracing` infra is implemented by:
- Introducing an optional `tracing` cargo feature in bootstrap.
- Added optional `tracing*` dependencies which are gated behind the `tracing` cargo feature.
- When `BOOTSTRAP_TRACING` is set, `bootstrap.py` will build bootstrap with `--features=tracing`.
There is a small trick here to share `BOOTSTRAP_TRACING` env var without having to add a separate env var:
- `BOOTSTRAP_TRACING=1` is not a registered `tracing` filter target, so that can be used to enable the `tracing` cargo feature yet not actually enable any tracing logs (useful for editor r-a setups without actually outputting any tracing logs).
- `BOOTSTRAP_TRACING=TRACE` and such are actually valid `tracing` filters, but that sets `BOOTSTRAP_TRACING` anyway.
Example usage: https://github.com/rust-lang/rust/pull/135299 (that experimental PR is not conditionally gated)
This PR is intentionally kept minimal to focus on the infra itself. To get actual mileage, instrumentations will need to be added to individual `Step`s and such.
r? `@onur-ozkan` (or reroll)
|
|
clean up code related to the rustdoc-js test suite
r? `@jieyouxu`
|
|
ci: added test log format for ci
This PR adds a new test render format specifically for ci.
The goal as stated in #134910 is to make reviewing test failures in CI easier.
See the new test output format in the CI for this PR ([here](https://github.com/rust-lang/rust/actions/runs/12723914643/job/35469515397?pr=135355))
closes #134910 cc: `@jyn514`
|
|
|
|
|
|
rustdoc: use import stability marker in display
Fixes #135078
|
|
The two implementations were identical, so there's no need to use a
trait method.
|
|
It's never overridden, so it shouldn't be on the trait.
|
|
Clang will not respect this value in cross configurations.
|
|
|
|
`BOOTSTRAP_TRACING` env var is set
|
|
|
|
|
|
run_make_support: add `#![warn(unreachable_pub)]`
This PR enables the [`unreachable_pub`](https://doc.rust-lang.org/rustc/lints/listing/allowed-by-default.html#unreachable-pub) lint as warn in the `run_make_support` crate.
Related to https://github.com/rust-lang/compiler-team/issues/773
r? ``@jieyouxu``
|
|
Deny various clippy lints
Almost all of these clippy lints have zero occurrences. Two of them have one each, and this PR fixes those.
|
|
rustdoc-json: Include items in stripped modules in `Crate::paths`.
Closes #135309
When we're running rustdoc-json, we should err on the side of adding more items to `Cache::paths`, as that directly becomes `Crate::paths` in the output.
r? ``@GuillaumeGomez.`` Best reviewed commit-by-commit.
|
|
|
|
|
