From: Robert Boyer <robertstephenboyer@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 69249@debbugs.gnu.org, rms@gnu.org
Subject: bug#69249: bug in native-compile?
Date: Mon, 19 Feb 2024 21:42:49 -0600 [thread overview]
Message-ID: <CAP9n0TPuVj-NgS8JH1Tz_04hK38Addipjj3EgC_De5LNZd1L=Q@mail.gmail.com> (raw)
In-Reply-To: <jwva5nvua1c.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]
> In the context of ELisp, for example, we wouldn't an incorrect type
declaration to risk crashing your editor, which limits significantly
what can be done and how we can do it.
I do not get your point. Errors are a horrible problem we face in every
part of all the code we run. Software that catches errors is a necessity,
but it does not work perfectly. I get blown away many times a day and have
to reboot my Chromebook. I cannot easily list all of the things I am
constantly watching out for: network service disconnection, spilling my
drink on my keyboard, power failures ..., relatives dying, doctors
appointments, ...
I regard errors from declarations as wonderful reports that usually show up
during SBCL compilation.
Bob
On Mon, Feb 19, 2024 at 8:51 PM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > However, I have been hacking Lisp hard since 1967, and to me the
> assertion
> > that a Lisp must support THE and DECLARE is about as obvious as the
> > assertion that doctors must wash their hands. An untold number of
> infants'
>
> There are several subtly different ways to interpret that assertion,
> actually, when you're working on the actual implementation of
> a compiler.
>
> In the context of ELisp, for example, we wouldn't an incorrect type
> declaration to risk crashing your editor, which limits significantly
> what can be done and how we can do it.
>
>
> Stefan
>
>
--
Anything I seem to state should be taken as a question. I am at least 77
and feeble.
[-- Attachment #2: Type: text/html, Size: 2098 bytes --]
prev parent reply other threads:[~2024-02-20 3:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 4:26 bug#69249: bug in native-compile? Robert Boyer
2024-02-18 19:44 ` Eli Zaretskii
2024-02-18 20:14 ` Robert Boyer
2024-02-18 21:28 ` Andreas Schwab
2024-02-18 22:19 ` Robert Boyer
2024-02-18 22:25 ` Robert Boyer
2024-02-18 22:39 ` Robert Boyer
2024-02-19 3:30 ` Eli Zaretskii
2024-02-19 3:58 ` Robert Boyer
2024-02-19 7:48 ` Andrea Corallo
2024-02-19 12:49 ` Eli Zaretskii
2024-02-18 22:45 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 23:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-18 23:42 ` Robert Boyer
2024-02-18 23:46 ` Robert Boyer
2024-02-19 15:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <CAP9n0TOTEZJy8VXeSyMZpT59u0a434_MiwBA0LrwgjH2xc44ww@mail.gmail.com>
2024-02-20 2:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-20 3:42 ` Robert Boyer [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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP9n0TPuVj-NgS8JH1Tz_04hK38Addipjj3EgC_De5LNZd1L=Q@mail.gmail.com' \
--to=robertstephenboyer@gmail.com \
--cc=69249@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).