diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-07-15 21:19:11 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-07-15 21:19:11 +0900 |
| commit | 98130137d95ca130dedd2501c2e6478734658683 (patch) | |
| tree | 5655f45c6314740fd1755dc63416fc54e86ae3e0 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs | |
| parent | 10f335fed17fb0ccbf0da903cffc7fd1aa57ec1b (diff) | |
| parent | 636fcacb447c65df4d5eda363218b979f11ce057 (diff) | |
| download | rust-98130137d95ca130dedd2501c2e6478734658683.tar.gz rust-98130137d95ca130dedd2501c2e6478734658683.zip | |
Rollup merge of #86478 - ehuss:future-incompat-test, r=oli-obk
Add -Zfuture-incompat-test to assist with testing future-incompat reports. This adds a `-Zfuture-incompat-test` cli flag to assist with testing future-incompatible reports. This flag causes all lints to be treated as a future-incompatible lint, and will emit a report for them. This is being added so that Cargo's testsuite can reliably test the reporting infrastructure. Right now, Cargo relies on using array_into_iter as a test subject. Since the breaking "future incompatible" lints are never intended to last forever, this means Cargo's testsuite would always need to keep changing to choose different lints (for example, #86330 proposed dropping that moniker for array_into_iter). With this flag, Cargo's tests can trigger any lint and check for the report.
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions