From: npostavs@users.sourceforge.net
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 27340@debbugs.gnu.org
Subject: bug#27340: 26.0.50; byte-compile-delete-errors value changes unexpectedly
Date: Mon, 12 Jun 2017 07:12:24 -0400 [thread overview]
Message-ID: <87wp8htq7b.fsf@users.sourceforge.net> (raw)
In-Reply-To: <b4mk24hqyzw.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 12 Jun 2017 19:30:43 +0900")
found 27340 25.2
tags 27340 + confirmed
quit
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> When loading a certain Lisp module that requires eieio, the value
> of `byte-compile-delete-errors' is changed to t (the default nil)
> unexpectedly.
[...]
> Though I don't know why it changes `byte-compile-delete-errors',
> I think it's a bug.
It's because of the 'cl-declaim' around that 'cl-defstruct':
(progn
;; Arrange for field access not to bother checking if the access is indeed
;; made to an eieio--class object.
(cl-declaim (optimize (safety 0)))
(cl-defstruct (eieio--class
...
)
;; Set it back to the default value.
(cl-declaim (optimize (safety 1))))
The problem is that the default (safety 1) value is not default with
respect to byte-compile-delete-errors:
(defun cl--do-proclaim (spec hist)
...
(let (...
(safety (assq (nth 1 (assq 'safety (cdr spec)))
'((0 t) (1 t) (2 t) (3 nil)))))
...
(if safety (setq cl--optimize-safety (car safety)
byte-compile-delete-errors (nth 1 safety)))))
next prev parent reply other threads:[~2017-06-12 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 10:30 bug#27340: 26.0.50; byte-compile-delete-errors value changes unexpectedly Katsumi Yamaoka
2017-06-12 11:12 ` npostavs [this message]
2017-06-15 8:49 ` Katsumi Yamaoka
2017-06-16 11:37 ` npostavs
2017-06-19 9:23 ` Katsumi Yamaoka
2017-06-24 14:19 ` npostavs
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=87wp8htq7b.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27340@debbugs.gnu.org \
--cc=yamaoka@jpl.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).