diff options
| author | Philipp Krones <hello@philkrones.com> | 2020-05-31 14:57:33 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-31 14:57:33 +0200 |
| commit | 873c9fc8f2f7cd04049d70fbc755b070a9c3a324 (patch) | |
| tree | 8abed531e559af37de04152e142e725bbeed026b /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs | |
| parent | 0fff522071c35f3af405bf64179dea41d7bcb1e1 (diff) | |
| parent | 64a05f56c33d4754808ef85e634f72a9053c56fd (diff) | |
| download | rust-873c9fc8f2f7cd04049d70fbc755b070a9c3a324.tar.gz rust-873c9fc8f2f7cd04049d70fbc755b070a9c3a324.zip | |
Rollup merge of #5656 - ebroto:len_zero_ranges, r=matthiaskrgr
len_zero: skip ranges if feature `range_is_empty` is not enabled If the feature is not enabled, calling `is_empty()` on a range is ambiguous. Moreover, the two possible resolutions are unstable methods, one inherent to the range and the other being part of the `ExactSizeIterator` trait. Since `len_zero` only checks for existing `is_empty()` inherent methods, we only take into account the `range_is_empty` feature. Related: https://github.com/rust-lang/rust/issues/48111#issuecomment-445132965 changelog: len_zero: avoid linting ranges without #![feature(range_is_empty)] Fixes: #3807
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions