From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Philipp Stephani <p.stephani2@gmail.com>,
25166@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#25166: 26.0.50; It shouldn't be possible to set the function cell of nil and t
Date: Fri, 27 Oct 2017 13:59:25 -0400 [thread overview]
Message-ID: <CAM-tV-9Z1xVauAsbo8k8X6KMEHvYV_JyxKVpNg4NzuYrVR6Zpw@mail.gmail.com> (raw)
In-Reply-To: <83ziewipb2.fsf@gnu.org>
# fset of nil is already covered in Bug#25110
retitle 25166 It shouldn't be possible to set the function cell of t
tags 25166 wontfix
close 25166
quit
On Mon, May 1, 2017 at 11:12 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Philipp Stephani <p.stephani2@gmail.com>
>> Date: Mon, 01 May 2017 14:44:44 +0000
>> Cc: rgm@gnu.org, 25166@debbugs.gnu.org
>>
>> Stefan Monnier <monnier@iro.umontreal.ca> schrieb am Mi., 28. Dez. 2016 um 00:11 Uhr:
>>
>> >> Because there doesn't seem to be any good reason to single out nil and
>> >> t in this respect and because those things aren't terribly dangerous.
>> > So therefore we shouldn't reinstate that now.
>>
>> Yes, that's my opinion.
>>
>> Well, my opinion is obviously different, so the maintainer should decide.
>
> One maintainer has already decided, see above.
Seems final enough, closing as wontfix.
PS for an example of why singling out nil makes sense (but this
doesn't apply to t) see [1].
Summary: (autoload #'nil "something" nil t) silently succeeds but
makes forward-word, backward-word, etc, (fail to) funcall nil.
[1]: https://github.com/jwiegley/use-package/issues/512
next prev parent reply other threads:[~2017-10-27 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 9:41 bug#25166: 26.0.50; It shouldn't be possible to set the function cell of nil and t Philipp
2016-12-11 18:38 ` Glenn Morris
2016-12-12 20:25 ` Glenn Morris
2016-12-26 19:29 ` Philipp Stephani
2016-12-26 19:41 ` Philipp Stephani
2016-12-26 19:47 ` Eli Zaretskii
2016-12-27 15:15 ` Stefan Monnier
2016-12-27 22:49 ` Eli Zaretskii
2016-12-27 23:11 ` Stefan Monnier
2017-05-01 14:44 ` Philipp Stephani
2017-05-01 15:12 ` Eli Zaretskii
2017-10-27 17:59 ` Noam Postavsky [this message]
2017-10-28 16:16 ` Stefan Monnier
2017-10-28 16:45 ` Noam Postavsky
2017-10-29 18:10 ` Stefan Monnier
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=CAM-tV-9Z1xVauAsbo8k8X6KMEHvYV_JyxKVpNg4NzuYrVR6Zpw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=25166@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.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).