Re: [PATCH] Accept alists when serializing JSON

[Vibhav Pant]

My motivation behind plist support was to achieve feature parity with json.el,
so that `json-serialize` could be used as a drop in replacement in the future.
I also had a patch to add support for functionality similar to what json.el
variables `json-false` and `json-null` apply, using keyword arguments to
`json-serialize` and `json-parse-*` (which is why I submitted the get_key_arg
patch earlier).

On Fri, Dec 22, 2017 at 7:25 PM, Philipp Stephani <address@hidden> wrote:
>
>
> Vibhav Pant <address@hidden> schrieb am Mi., 20. Dez. 2017 um 06:58 Uhr:
>>
>>
>> do you think that we can add plist support in the future?
>>
> In theory yes, but I don't think it's worth the additional complexity.
> Plists are not a general-purpose data structure; they are mostly used in a
> specialized way, e.g. for keyword arguments or symbol properties. Supporting
> alists make sense, they are easy to work with due to let-alist and other
> alist-specific functionality. But that's not the case for plists.
> Or do you have a specific use case where plist support would provide a
> significant advantage?



-- 
Vibhav Pant
address@hidden