doc: A note about internally-tagged enums not supported #231
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Internally-tagged enums are extremely useful and therefore used quite a lot in the wild. It's a bit of a shock to users to learn (the hard way) that they're not supported by `csv`. So it'd be great to at least document this limitation in the docs.
|
@BurntSushi could you please have a look? |
|
@BurntSushi Given that you explicitly asked me for this PR and it's a simple change that will likely help a lot of people avoid bumping into the serious and unexpected limitation, ignoring it for years, is very disrespectful to say the least. 😔 |
|
I just found this ticket after trying to get internally tagged enums to work... it'd be really nice if this was merged to at least warn users about the limitations 🙄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Internally-tagged enums are extremely useful and therefore used quite a lot in the wild. It's a bit of a shock to users to learn (the hard way) that they're not supported by
csv. So it'd be great to at least document this limitation in the docs.