span: allow ambiguous_negative_literals
#51
Merged
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.
This was bad timing. The lang team just stabilized (in nightly) a new
deny-by-default lint, named
ambiguous_negative_literals
, whichtriggers an error for things like
-1.hour()
. While such things can beconfusingly ambiguous in some cases, in Jiff,
-1.hour()
,(-1).hour()
and
-(1.hour())
are all, very intentionally, precisely equivalent.For now we just
allow
the lint. If the lint stays, we'll likely wantto recommend allowing it in the Jiff docs.
See: rust-lang/rust#121364