len_zero: skip ranges if feature range_is_empty
is not enabled
#5656
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 theExactSizeIterator
trait.Since
len_zero
only checks for existingis_empty()
inherent methods, we only take into account therange_is_empty
feature.Related: rust-lang/rust#48111 (comment)
changelog: len_zero: avoid linting ranges without #![feature(range_is_empty)]
Fixes: #3807