Close #121

[laralove143]

No description provided.

[djc]

This mostly looks good. Can you please give the existing commit a meaningful commit message, and add a comment that bumps the version number for chrono-tz because this is a semver-incompatible change?

[laralove143]

I don't know how to edit a commit message after a push

[djc]

Well, you could have googled it. Try git rebase -i main and put an r (for reword) next to both of your commits. It should bring up your editor for both commits, move the commit message on the second commit to the first commit and change the second commit to something like "Bump version for semver-incompatible changes".

[pitdicker]

I'd like to reopen this PR. It was closed because the author deleted his fork of the repo.

But I'm not a fan of enums that change depending on the crate features. And we should especially not remove the Copy implementation when the std feature is enabled.

@djc Does it give any benefit to include the string that failed to parse? It is passed to from_str by reference so the user can easily wrap it with something like anyhows with_context.

[djc]

Leaving the string out of seems reasonable.