> Are you aware of *print-dup* ? It causes the printer to > preserve more of the specific type information than normal > printing:
It's one of those things that hasn't yet crept close enough on my radar for me to absorb. This is the impetus... > Having said that, it's important to note it doesn't help > your original scenario, because *print-dup* doesn't support > struct maps (yet): Ah, good and bad :) I expect there are plenty of dangerous edge cases to handle -- e.g., what to do if there is no struct by that name, or if it's a different struct with the same name. I suspect that in my case the right approach is either to switch to pure maps (which round-trip perfectly), or to take more control over the upstream serialization, and produce a (struct foo ...) form instead of just prn-ing the struct-map. I started down the avenue of converting maps into struct-maps, though, so perhaps I'll see how that turns out. This data is accessed much more often than it's loaded, so the overhead is likely worthwhile. Thanks for the discussion! -R --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
