From: Chong Yidong <cyd@stupidchicken.com>
To: Teodor Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Hash table read syntax
Date: Tue, 22 Dec 2009 14:17:07 -0500 [thread overview]
Message-ID: <87fx72akek.fsf@stupidchicken.com> (raw)
I think there's a problem with the design of the hash table read syntax:
(make-hash-table)
#s(hash-table size 65 test eql rehash-size 1.5 rehash-threshold 0.8 data ())
The plist ought to use `:size', `:test', `:rehash-size', etc., rather
than `size', `test', `rehash-size', etc. Otherwise, it's inconsistent
with the arguments to `make-hash-table', which uses `:size', `:test',...
I would like to make this change now, before it becomes "official" with
the Emacs 23.2 release. Any objections?
next reply other threads:[~2009-12-22 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 19:17 Chong Yidong [this message]
2009-12-22 19:31 ` Hash table read syntax Chong Yidong
2009-12-22 22:03 ` Ted Zlatanov
2009-12-23 10:31 ` Stephen J. Turnbull
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fx72akek.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).