fitzgen opened Issue #1705:
Right now we use
derive(Serialize, Deserialize)
but this results in some unnecessary data being [de]serialized: themap
member.Instead, if we implement [de]serialization by hand, we can serialize the interned integers in order of their id and then recreate the
map
member on the fly during deserialization. This is what we do for thePathInterner
, for example.This would result in smaller serialized automata generated by peepmatic.
fitzgen labeled Issue #1705:
Right now we use
derive(Serialize, Deserialize)
but this results in some unnecessary data being [de]serialized: themap
member.Instead, if we implement [de]serialization by hand, we can serialize the interned integers in order of their id and then recreate the
map
member on the fly during deserialization. This is what we do for thePathInterner
, for example.This would result in smaller serialized automata generated by peepmatic.
declanvk commented on Issue #1705:
@fitzgen
Hello, I was interested in
peepmatic
and I saw this category of issues, so I thought I would attempt some of the easier ones.I have a PR for this issue (#1944). If more PRs in this area would be welcome/un-welcome, please let me know.
fitzgen closed Issue #1705:
Right now we use
derive(Serialize, Deserialize)
but this results in some unnecessary data being [de]serialized: themap
member.Instead, if we implement [de]serialization by hand, we can serialize the interned integers in order of their id and then recreate the
map
member on the fly during deserialization. This is what we do for thePathInterner
, for example.This would result in smaller serialized automata generated by peepmatic.
fitzgen commented on Issue #1705:
Hi @declanvk! Glad to hear of your interest. Yes, more PRs are very welcome, thanks :)
Last updated: Dec 23 2024 at 12:05 UTC