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
Is there any technical reason behind Set support absence?
Or I'm a very first person who actually needs it?
If it's missed because no one needs it yet, and maintainers are not against it, I would like to provide pull request with such implementation. Documentation and tests included.
Hopefully, new minor release would be issued after this contribution.
Thoughts?
Regards,
Artem.
The text was updated successfully, but these errors were encountered:
I'm not against, of course. Did not include it, because generally, when you get something from internet in json, it is definitely does not include sets, instead it has list/array, and then you check that members of this set is uniq and then call set, like t.List() & uniq & set.
To check python structs, you can use t.Type(set).
Not sure what is you case, I'm open to new contributions.
Hi, thanks for the useful package!
Is there any technical reason behind
Set
support absence?Or I'm a very first person who actually needs it?
If it's missed because no one needs it yet, and maintainers are not against it, I would like to provide pull request with such implementation. Documentation and tests included.
Hopefully, new minor release would be issued after this contribution.
Thoughts?
Regards,
Artem.
The text was updated successfully, but these errors were encountered: