about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2023-06-23 19:40:00 +0200
committerGitHub <noreply@github.com>2023-06-23 19:40:00 +0200
commit4821f807160fa9ab6d843ef2ea37d5f2bd760a19 (patch)
tree059973964407e3c9da810c21f5af5c6177792acf /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parentc9139521e75090aa28aa4d1a2e06c74f66878059 (diff)
parent752fb52ae94cfb36bb01dff5b2b31134605a7da3 (diff)
downloadrust-4821f807160fa9ab6d843ef2ea37d5f2bd760a19.tar.gz
rust-4821f807160fa9ab6d843ef2ea37d5f2bd760a19.zip
Rollup merge of #112960 - GuillaumeGomez:rustdoc-files-check, r=notriddle
[tests/rustdoc] Add @files command

The ``````@!has`````` checks is very problematic as it wouldn't catch if the file scheme is updated and the file is generated again. ``````@files`````` allows to ensure that the given folder contains exactly the provided entries (files and folders).

I'm wondering if we should forbid the ``````@!has`````` for files. To be discussed after this PR I suppose.

r? `````@notriddle`````
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions