You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be documented whether or not extra::time functions can go backwards in time. One reasonable way for that to happen for some functions might be that the user changes the time settings.
The text was updated successfully, but these errors were encountered:
Visiting for triage. Since extra::time (now libtime) will eventually be replaced by something (rust-chrono?) (cf #14657), should this be closed and filed under the replacement (provided it persists there)?
uninlined_format_args: do not inline argument with generic parameters
Fixrust-lang#10339
---
changelog: FP: [`uninlined_format_args`]: No longer lints for arguments with generic parameters
[rust-lang#10343](rust-lang/rust-clippy#10343)
<!-- changelog_checked -->
It should be documented whether or not extra::time functions can go backwards in time. One reasonable way for that to happen for some functions might be that the user changes the time settings.
The text was updated successfully, but these errors were encountered: