unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 61f8c23 1/2: Minor advice.el fix
Date: Fri, 23 Dec 2016 12:20:55 +0000	[thread overview]
Message-ID: <CAArVCkRTqSHhK__sfs=e0hPG+snAMEsEBpZMKM33c_XZpop5Ow@mail.gmail.com> (raw)
In-Reply-To: <jwv1sx5gfob.fsf-monnier+Inbox@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> schrieb am So., 18. Dez. 2016 um
21:15 Uhr:

> > For some of them definitely. I'd draw the line between pure functions
> like
> > car and eq, where those facilities never make sense and would be
> > ineffective anyway as the functions are compiled away or called directly,
> > and impure functions like call-process, where fset is necessary for
> > mocking. As a rule of thumb, I'd suggest to ban fset on all symbols that
> > have a byte-code equivalent, and on constant symbols.
>
> I still very doubt that the potential benefit is worth the added cost
> (more specifically, as a maintainer I would strongly oppose such
> measure).


Why is then the potential benefit for the value cells worth the added cost,
i.e. why not also allow (set t 5)?


> Are you also going to try and prevent the user from using all
> the other ways he can shoot himself in the foot?
>
>
To the extent that it's feasible, yes. Emacs Lisp isn't C. If the user
wants to shoot themselves in the foot, they can write a C module.

[-- Attachment #2: Type: text/html, Size: 1757 bytes --]

  reply	other threads:[~2016-12-23 12:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161212202151.21054.37035@vcs.savannah.gnu.org>
     [not found] ` <20161212202152.428192201BB@vcs.savannah.gnu.org>
2016-12-13 13:40   ` [Emacs-diffs] master 61f8c23 1/2: Minor advice.el fix Stefan Monnier
2016-12-14 16:49     ` Glenn Morris
2016-12-14 18:15       ` Stefan Monnier
2016-12-17 21:11     ` Philipp Stephani
2016-12-17 22:08       ` Stefan Monnier
2016-12-18 19:43         ` Philipp Stephani
2016-12-18 20:15           ` Stefan Monnier
2016-12-23 12:20             ` Philipp Stephani [this message]
2016-12-24  1:21               ` 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='CAArVCkRTqSHhK__sfs=e0hPG+snAMEsEBpZMKM33c_XZpop5Ow@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).