From: Sho Takemori <stakemorii@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 23528@debbugs.gnu.org
Subject: bug#23528: 25.0.93; Errors are ignored if I load eieio and evaluate the byte-compiled form
Date: Sun, 15 May 2016 15:37:34 +0900 [thread overview]
Message-ID: <CAHbQ=cWUSk4k02KNGNUybHmYUDXmjD5nZe8XC7zbC=0dex-jEg@mail.gmail.com> (raw)
In-Reply-To: <87ziru0ybs.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Thanks for the comment. I didn't know about `byte-compile-delete-errors'.
Btw, why is your comment not displayed at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23528?
Sho Takemori
2016-05-14 0:31 GMT+09:00 Michael Heerdegen <michael_heerdegen@web.de>:
> Sho Takemori <stakemorii@gmail.com> writes:
>
> > eieio-core.el
> > (progn
> > (require 'cl-lib)
> > ;; Arrange for field access not to bother checking if the access is
> indeed
> > ;; made to an eieio--class object.
> > (cl-declaim (optimize (safety 0)))
> > [...]
>
> > ;; Set it back to the default value.
> > (cl-declaim (optimize (safety 1))))
>
> Thanks for investigating.
>
> Looks like loading "eieio-core" can permanently change the value of
> `byte-compile-delete-errors'.
>
> And at least, the last declaim form should be
>
> (cl-declaim (optimize (safety 3)))
> ^
> to have the desired effect of setting `byte-compile-delete-errors' to
> nil.
>
> Can someone with knowledge of eieio please care about this?
>
>
> Thanks,
>
> Michael.
>
[-- Attachment #2: Type: text/html, Size: 1687 bytes --]
next prev parent reply other threads:[~2016-05-15 6:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 11:45 bug#23528: Subject: 25.0.93; Errors are ignored if I load eieio and evaluate the byte-compiled form Sho Takemori
2016-05-13 13:50 ` bug#23528: " Sho Takemori
2016-05-13 15:31 ` Michael Heerdegen
2016-05-15 6:37 ` Sho Takemori [this message]
2016-05-15 14:06 ` Michael Heerdegen
2018-02-10 3:09 ` bug#23528: Subject: " Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHbQ=cWUSk4k02KNGNUybHmYUDXmjD5nZe8XC7zbC=0dex-jEg@mail.gmail.com' \
--to=stakemorii@gmail.com \
--cc=23528@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.