From: Ivan Sokolov <ivan-p-sokolov@ya.ru>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 47875@debbugs.gnu.org
Subject: bug#47875: Elisp reader doesn't handle keywords
Date: Sun, 06 Jun 2021 21:21:39 +0300 [thread overview]
Message-ID: <875yyqonv0.fsf@ya.ru> (raw)
In-Reply-To: <479aeb7313571f434ef146f5aa3e5b120a1593ad.camel@student.tugraz.at> (Leo Prikler's message of "Sat, 05 Jun 2021 23:14:25 +0200")
Leo Prikler <leo.prikler@student.tugraz.at> writes:
> You could define Elisp symbolp as
> (lambda (thing)
> (or (funcall (@ (guile) symbol?) thing)
> (funcall (@ (guile) keyword?) thing)))
You are right, I haven't thought about changing the implementaion of
symbolp.
> but perhaps there's an even faster way to check this property.
Use guile-primitive instead of guile-ref? Both symbol? and keyword? are
primitives.
prev parent reply other threads:[~2021-06-06 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 16:05 bug#47875: Elisp reader doesn't handle keywords Leo Prikler
2021-05-13 22:43 ` Taylan Kammer
2021-06-04 12:13 ` Ivan Sokolov
[not found] ` <87lf7onwcp.fsf@ya.ru>
2021-06-05 21:14 ` Leo Prikler
2021-06-06 18:21 ` Ivan Sokolov [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yyqonv0.fsf@ya.ru \
--to=ivan-p-sokolov@ya.ru \
--cc=47875@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).