From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: hash-consing bignums and eq==eql
Date: Sat, 08 Sep 2018 23:09:54 -0400 [thread overview]
Message-ID: <jwv8t4bfjzp.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 075ee700-d431-9434-c9d9-a7b3ae3f17fa@cs.ucla.edu
> Common Lisp and Scheme both have this distinction, and they seem to be doing
> OK.
Don't forget that Common Lisp and Scheme have a very different user-base
and goals. These are languages whose target users are real programmers,
and where its considered normal to let a program core-dump if the
programmer has given incorrect compiler hints in the form of
type annotations.
Most users of Elisp on the other hand would not describe themselves as
programmers.
> In this particular tradeoff between performance and nicer behavior, most
> Lisp users seem to prefer performance.
If they prefer performance, they won't be coding in Elisp, I'm afraid.
Stefan
next prev parent reply other threads:[~2018-09-09 3:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180821204437.16880.99611@vcs0.savannah.gnu.org>
[not found] ` <20180821204439.62390209A6@vcs0.savannah.gnu.org>
2018-08-22 12:36 ` [Emacs-diffs] master f18af6c: Audit use of lsh and fix glitches Pip Cet
2018-08-22 13:35 ` Ken Brown
2018-08-22 13:44 ` Paul Eggert
2018-08-22 15:50 ` Pip Cet
2018-08-22 17:27 ` Paul Eggert
2018-08-22 20:05 ` Pip Cet
2018-08-22 21:53 ` Paul Eggert
2018-08-22 20:45 ` Stefan Monnier
2018-08-23 14:55 ` Pip Cet
2018-08-23 15:56 ` Stefan Monnier
2018-08-24 18:00 ` Pip Cet
2018-08-24 20:55 ` Paul Eggert
2018-08-25 15:02 ` Pip Cet
2018-08-25 18:02 ` Stefan Monnier
2018-08-25 21:24 ` Paul Eggert
2018-08-28 14:08 ` hash-consing bignums and eq==eql Stefan Monnier
2018-08-29 13:32 ` Pip Cet
2018-08-29 19:23 ` Stefan Monnier
2018-08-29 19:31 ` Paul Eggert
2018-08-29 20:50 ` Stefan Monnier
2018-09-09 3:09 ` Stefan Monnier [this message]
2018-09-09 6:26 ` Paul Eggert
2018-08-22 13:49 ` [Emacs-diffs] master f18af6c: Audit use of lsh and fix glitches Pip Cet
2018-08-22 14:52 ` Eli Zaretskii
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=jwv8t4bfjzp.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).