SerAPI represents struct fields as (name value) (inheriting that behavior from Sexplib, I think), while serde-lexpr represents them as (name . value).
To make serde-lexpr compatible with more kinds of S-expressions, would it make sense to add a customization option that controls which way struct fields are represented? This seems comparable to how serde allows configuration about how enums should be tagged.
SerAPI represents struct fields as
(name value)(inheriting that behavior from Sexplib, I think), while serde-lexpr represents them as(name . value).To make serde-lexpr compatible with more kinds of S-expressions, would it make sense to add a customization option that controls which way struct fields are represented? This seems comparable to how
serdeallows configuration about how enums should be tagged.