diff options
| author | Philipp Krones <hello@philkrones.com> | 2020-07-13 15:59:42 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-13 15:59:42 +0200 |
| commit | 019e281d158c5ee8b0d90c2b1e0347a512d211da (patch) | |
| tree | 1d5487001075cf25824a8faf96ce104d9daccce1 /src/rustllvm/CoverageMappingWrapper.cpp | |
| parent | 75d43aac73df6086ab9566a39d5ea7afe70d89c9 (diff) | |
| parent | afa4148cc6dee0f9e0ca5b33f2511b9305d84fcb (diff) | |
| download | rust-019e281d158c5ee8b0d90c2b1e0347a512d211da.tar.gz rust-019e281d158c5ee8b0d90c2b1e0347a512d211da.zip | |
Rollup merge of #5752 - chrisduerr:pedantic_ranges, r=flip1995
Move range_minus_one to pedantic This moves the range_minus_one lint to the pedantic category, so there will not be any warnings emitted by default. This should work around problems where the suggestion is impossible to resolve due to the range consumer only accepting a specific range implementation, rather than the `RangeBounds` trait (see #3307). While it is possible to work around this by extracting the boundary into a variable, I don't think clippy should encourage people to disable or work around lints, but instead the lints should be fixable. So hopefully this will help until a proper implementation checks what the range is used for. *Please keep the line below* changelog: move [`range_minus_one`] to pedantic
Diffstat (limited to 'src/rustllvm/CoverageMappingWrapper.cpp')
0 files changed, 0 insertions, 0 deletions