Re: [PATCH] json: Add support for encoding structs

[Stefan Monnier]

> Maybe one way is to distinguish '(:serialize-field nil) from '() by
> checking with memq for the key?

FWIW, while you can make this work, I think it's a bad API: Elisp
usually behaves like "an absent argument is equivalent to nil", and it's
easier for the coder if we stick to this behavior (also, occasionally
it's handy to be able to use ":key nil" in order not to pass :key).

> IIRC, the empty string is a valid JSON key (`JSON.parse(`{"":1}`)`
> works in JS).  Symbols are also considered a valid type according to
> `json-encode-key'.

I don't see why that forces us to also accept symbols here.


        Stefan