Swap MappedLocalTime
and LocalResult
type alias
#1547
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.
In #1501 I thought renaming
LocalResult
toMappedLocalTime
would be entirely without consequences as long as there is a type alias with the old name. Turns out there is one case where a type alias behaves differently 😞. You can't import enum variants from a type alias withuse chrono::LocalResult::*
.We have two choices:
LocalResult
, and use the type alias everywhere else.The second choice has my preference. The docs look mostly sane, but break down once you come to the trait implementations section:
...