[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JSON->lisp Mapping: Hash vs AList
From: |
Stefan Monnier |
Subject: |
Re: JSON->lisp Mapping: Hash vs AList |
Date: |
Sat, 16 Dec 2017 21:41:48 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> I don't like optional arguments. They make the call sites less readable,
> because it becomes less clear what the meaning of an argument is.
> I don't care about saving a few nanoseconds; that's premature optimization.
I was talking about the general design of Elisp, and in that context
I do not think it can qualify as premature optimization.
But in any case, it's a bit late to change that design, I think.
Stefan
- Re: JSON->lisp Mapping: Hash vs AList, (continued)
- Re: JSON->lisp Mapping: Hash vs AList, Philipp Stephani, 2017/12/16
- [PATCH] Accept alists when serializing JSON, Philipp Stephani, 2017/12/18
- Re: [PATCH] Accept alists when serializing JSON, Vibhav Pant, 2017/12/20
- Re: [PATCH] Accept alists when serializing JSON, Philipp Stephani, 2017/12/22
- Re: [PATCH] Accept alists when serializing JSON, Vibhav Pant, 2017/12/24
- Re: [PATCH] Accept alists when serializing JSON, Philipp Stephani, 2017/12/26
- Re: [PATCH] Accept alists when serializing JSON, Philipp Stephani, 2017/12/24
Re: JSON->lisp Mapping: Hash vs AList, Stefan Monnier, 2017/12/16