In my initial commit, I'm keeping the visibility level of the new Serializer at "internal" so the API surface is equivalent to the previous code.
However, would you have any concerns about making Serializer be public? It might help me with a project I'm working on.
(Actually, what I really want is to add additional rows to an existing file. I'm still working out the design, so it's not clear yet whether I should append rows to my DataView and serialize the whole thing, or go directly to the file APIs to write out only the new rows.)
Let's keep the Serializer internal for now. You've raised many good points about appending or exporting rows, so I've moved that to a separate discussion.
In my initial commit, I'm keeping the visibility level of the new Serializer at "internal" so the API surface is equivalent to the previous code.
However, would you have any concerns about making Serializer be public? It might help me with a project I'm working on.
(Actually, what I really want is to add additional rows to an existing file. I'm still working out the design, so it's not clear yet whether I should append rows to my DataView and serialize the whole thing, or go directly to the file APIs to write out only the new rows.)