about summary refs log tree commit diff
path: root/compiler/rustc_pattern_analysis/src
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-06-20 07:52:45 +0200
committerGitHub <noreply@github.com>2024-06-20 07:52:45 +0200
commitaf073e4e88629e70f4194fcd43b48a8c5b411029 (patch)
tree62b7dbd13b44c67bcf72000370d090cf4fab4010 /compiler/rustc_pattern_analysis/src
parent03d558f5b6de84d8aba5af5ac5dd2d21181eaad6 (diff)
parent95e214d6e5cbacd4bcc12f449674dbcc3f409a02 (diff)
downloadrust-af073e4e88629e70f4194fcd43b48a8c5b411029.tar.gz
rust-af073e4e88629e70f4194fcd43b48a8c5b411029.zip
Rollup merge of #126703 - the8472:on-blackbox-crypto-use, r=scottmcm
reword the hint::blackbox non-guarantees

People were tripped up by the "precludes", interpreting it that this function must not ever be used in cryptographic contexts rather than the std lib merely making zero promises about it being fit-for-purpose.

What remains unchanged is that if someone does try to use it *despite the warnings* then it is on them to pin their compiler versions and verify the assembly of every single binary build they do.
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions