docs: Use mdbook admonitions - #17384
Conversation
|
r? @weihanglo rustbot has assigned @weihanglo. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
I was planning to do it tonight as well. I am glad I haven't yet started |
|
Been meaning to do this ever since it came up |
There was a problem hiding this comment.
Some other "tips" need to update:
cargo/doc/book/src/reference/environment-variables.md
Lines 387 to 390 in 9243bb7
cargo/doc/contrib/src/process/working-on-cargo.md
Lines 133 to 135 in 9243bb7
|
So looks like And the memory usage seems to go unbound. |
|
So # works
env RUSTFLAGS=-Znext-solver=coherence cargo +nightly-2026-08-22 check -p varisat
# stuck
env RUSTFLAGS=-Znext-solver=globally cargo +nightly-2026-08-22 check -p varisatso something worth reporting to rust-lang/rust#160895. |
…ng#17385) ### What does this PR try to resolve? next trait resolver might have bugs dealing with it, but anyway we care less about intra doclinks for resolver-tests, and it anyway builds in clippy jobs. ### How to test and review this PR? See <rust-lang#17384 (comment)>: ``` # works env RUSTFLAGS=-Znext-solver=coherence cargo +nightly-2026-08-22 check -p varisat # stuck env RUSTFLAGS=-Znext-solver=globally cargo +nightly-2026-08-22 check -p varisat ```
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
Update cargo submodule 7 commits in e8cb624d5701824f46a2ec5873cfd59ee3d2f66c..94ba974179df2adb3c911fadf361f03b84aa8f14 2026-08-22 00:23:45 +0000 to 2026-08-25 18:16:11 +0000 - feat(diag): Stabilize cargo-lints (rust-lang/cargo#17298) - chore(deps): Update partial_ref to v0.3.4 (rust-lang/cargo#17392) - refactor: remove ad-hoc `subslice_range` (rust-lang/cargo#17390) - docs(changelog): move build-dir new layout to Changed (rust-lang/cargo#17387) - chore(deps): update msrv (1 version) to v1.98 (rust-lang/cargo#17386) - docs: Use mdbook admonitions (rust-lang/cargo#17384) - chore(ci): exclude resolver-tests from intra doc link checks (rust-lang/cargo#17385)
What does this PR try to resolve?
Establishing a pattern of their use which should reduce needing review feedback like #17382 (comment)
See https://rust-lang.github.io/mdBook/format/markdown.html#admonitions
How to test and review this PR?