would be nice to be able to customize serialization per value, ex have some specialized maps serialized as an array of values. I know you can do that with Records for instance but not regular maps
Then I guess it's all trade-offs, could be done with extend-with-metadata? true, but at a (performance) price
if you have a better way to do this, I am all ears
@dnolen has joined the channel
Thanks for looking into the metadata-on-symbol issue. Another issue I've worked around for a long time is the slow serialization of big maps. https://github.com/cognitect/transit-clj/issues/43 No hurry, since my current workaround still works, but it seems this issue is related: https://github.com/cognitect/transit-clj/issues/46
yeah, I think that's one of the highest priority issues in there. from a broad perspective, consumers have different needs re flushing frequency. I don't know what the answer will be on that but it is definitely something I think we should work on
Quick comment in passing. I think python-transit has compatibility issues with python 3.10. Something to do with the collection module.
for any issues like this, it's best to file an issue on the impl repo for tracking
https://github.com/cognitect/transit-python/issues for example
python unfortunately is one where we've a series of maintainers over the years, none of whom still work at Cognitect