Re: Check whether an object is an alist

[Heime <heimeborgia@protonmail.com>]

Sent with Proton Mail secure email.

On Wednesday, September 18th, 2024 at 9:02 AM, Heime <heimeborgia@protonmail.com> wrote:

> 
> 
> 
> 
> 
> Sent with Proton Mail secure email.
> 
> 
> On Wednesday, September 18th, 2024 at 7:35 AM, tomas@tuxteam.de tomas@tuxteam.de wrote:
> 
> > On Tue, Sep 17, 2024 at 07:20:22PM +0000, Heime wrote:
> > 
> > > On Wednesday, September 18th, 2024 at 6:28 AM, tomas@tuxteam.de tomas@tuxteam.de wrote:
> > > 
> > > > On Tue, Sep 17, 2024 at 06:04:41PM +0000, Heime wrote:
> > > > 
> > > > > On Wednesday, September 18th, 2024 at 5:57 AM, tomas@tuxteam.de tomas@tuxteam.de wrote:
> > > > 
> > > > > > [...] as an exercise for the reader.
> > > > > 
> > > > > (cl-every #'consp '((foo . bar) nil (baz . quux)))
> > > > 
> > > > Yes.
> > > > --
> > > > t
> > > 
> > > Have done this small test, and even though there is a nil (or anything
> > > else, e.g. jarod), assoc still works on the other keys.
> > 
> > That's what I was saying (and what Elisp's doc, which is recommended
> > reading also says). There are different views on that, and Elisp
> > itself is one of the less strict: it just ignores list elements which
> > aren't assocs.
> > 
> > There is some historical background to that. "Classical" Lisp "types"
> > are just defined by the operations defined on them.
> > 
> > Cheers
> > --
> > t
> 
> 
> After changing to the following, I am getting validation for list
> element (1 2 3), even though it is not an association.
> 
> (defun torium-alist-p (obj)
> "Return t if object OBJ is an association list (alist)."
> (and (listp obj)
> (cl-every (lambda (x) #'consp) obj)))

I remember.  No requirements of lambda to run #'consp on obj

Thus, again

(defun torium-alist-p (obj)
  "Return t if object OBJ is an association list (alist)."
  (and (listp obj)
       (cl-every #'consp obj)))