about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2023-12-06 17:21:59 +0100
committerGitHub <noreply@github.com>2023-12-06 17:21:59 +0100
commit95efc0d6e6ec8c0f026e77b1791f4abf9c29ee3b (patch)
tree074ed67784f415cd097c228fccfd4b564c1ea5ff /compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp
parent756bc44949290356f4aca4505dea8ea838bb861e (diff)
parentdc0f7a1208ad3e86b00cd8ee6aabffd8fd1d52b0 (diff)
downloadrust-95efc0d6e6ec8c0f026e77b1791f4abf9c29ee3b.tar.gz
rust-95efc0d6e6ec8c0f026e77b1791f4abf9c29ee3b.zip
Rollup merge of #118664 - notriddle:master, r=Mark-Simulacrum
docs: remove #110800 from release notes

It's not stable yet, and shouldn't be mentioned here. At least, the message shouldn't be written like this.

I realize it's weird to go through an FCP, and then have the feature remain unstable, but this was an unusual case.

Rustdoc used to silently swallow unknown language tokens on code blocks, and now it produces a compatibility warning. The FCP got everyone's sign-off on the warning, not the finished feature, which remains unstable.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/ArchiveWrapper.cpp')
0 files changed, 0 insertions, 0 deletions