about summary refs log tree commit diff
path: root/src/rustllvm/PassWrapper.cpp
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2017-09-21 09:41:26 +0000
committerbors <bors@rust-lang.org>2017-09-21 09:41:26 +0000
commit35edf7d8cbd49aa4ea516c6b60615927a722dfd6 (patch)
tree278fa197c9326159eaed1cba20e38fd10c0ed82f /src/rustllvm/PassWrapper.cpp
parente2504cfc7615b9247d4546672e31a9803f4b88ba (diff)
parentd02ceacb25d851a0dce67a3120f247558493c6ad (diff)
downloadrust-35edf7d8cbd49aa4ea516c6b60615927a722dfd6.tar.gz
rust-35edf7d8cbd49aa4ea516c6b60615927a722dfd6.zip
Auto merge of #44627 - zackmdavis:the_capgate_perogative, r=nrc
`--cap-lints allow` switches off `can_emit_warnings`

This boolean field on the error `Handler` is toggled to silence
warnings when `-A warnings` is passed. (This is actually a separate
mechanism from the global lint level—whether there's some redundancy
to be factored away here is an important question, but not one we
concern ourselves with in this commit.)  But the same rationale
applies for `--cap-lints allow`. In particular, this makes the "soft"
feature-gate warning introduced in 8492ad24 (which is not a lint, but
just calls `struct_span_warn`) not pollute the builds of dependent
crates.

Thanks to @kennytm for pointing out the potential of
`can_emit_warnings` for this purpose.

Resolves #44213.
Diffstat (limited to 'src/rustllvm/PassWrapper.cpp')
0 files changed, 0 insertions, 0 deletions