Closed nmathewson closed 1 year ago
I would prefer not to support this in this crate, but it would be reasonable for someone else to maintain a more fully featured implementation that exposes tags as a list. Alternatively you could wrap typetag::deserialize
in your own macro that also keeps track of its own list of tags.
Thanks for the useful crate!
Would you accept an MR for a feature to enumerate or inspect the list of supported tags? And if so, what would you want the API to look like?
Here are our use-cases: