From: Heime <heimeborgia@protonmail.com>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: Check whether an object is an alist
Date: Tue, 17 Sep 2024 19:20:22 +0000 [thread overview]
Message-ID: <PiMCU_iJePObgEwn7gnusyPeTiBdUSKtvdZTA515_CPT6IBQNkrbtvcsrReGHR15NNGjpCsXpJMOb1ZGCpTRifGIG6huuQIesxiuTLpdWEQ=@protonmail.com> (raw)
In-Reply-To: <ZunKTtSIRp5tLT8E@tuxteam.de>
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. This means that
one can still be able to get correct values even if the object is not
a complete alist. In a sense, if I am looking for keys in an object,
even though it is not an alist in a strict sense, things might still
work correctly. Is this the reason there does not exist an alistp ?
Or because traversing the list would be expensive ?
But if we want to be strict that an alist is a list of cons cells
with pairs of values, then only t1 should be accepted.
(let ( (t1 '((foo . bar) (alice . bob) (baz . qux)))
(t2 '((foo . bar) nil (alice . bob) (baz . qux)))
(t3 '((foo . bar) jarod (alice . bob) (baz . qux))) )
(message "%s" (assoc 'foo t1))
(message "%s" (assoc 'alice t2))
(message "%s" (assoc 'baz t3)) )
(foo . bar)
(alice . bob)
(baz . qux)
next prev parent reply other threads:[~2024-09-17 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 10:29 Check whether an object is an alist Heime
2024-09-17 8:45 ` Heime
2024-09-17 9:38 ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-09-17 9:46 ` tomas
2024-09-17 11:16 ` Heime
2024-09-17 11:23 ` tomas
2024-09-17 13:51 ` Heime
2024-09-17 13:58 ` tomas
2024-09-17 14:32 ` Heime
2024-09-17 15:20 ` tomas
2024-09-17 16:26 ` Heime
2024-09-17 17:57 ` tomas
2024-09-17 18:04 ` Heime
2024-09-17 18:28 ` tomas
2024-09-17 19:20 ` Heime [this message]
2024-09-17 19:35 ` tomas
2024-09-17 21:02 ` Heime
2024-09-17 21:25 ` Heime
2024-09-18 4:21 ` tomas
2024-09-18 4:52 ` Heime
2024-09-17 22:01 ` Stephen Berman
2024-09-17 19:22 ` [External] : " Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='PiMCU_iJePObgEwn7gnusyPeTiBdUSKtvdZTA515_CPT6IBQNkrbtvcsrReGHR15NNGjpCsXpJMOb1ZGCpTRifGIG6huuQIesxiuTLpdWEQ=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.