From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: problems with Emacs 28
Date: Sat, 31 Oct 2020 19:26:19 +0100 [thread overview]
Message-ID: <87v9eqntf8.fsf@zoho.eu> (raw)
In-Reply-To: jwv5z6ufexe.fsf-monnier+emacs@gnu.org
Stefan Monnier wrote:
>>> side-effect free - the function doesn't do any changes to
>>> anything, this implies non-destructiveness
>>
>> Which is also known as a 'pure' function.
>
> Are `gensym` and `current-time` side-effect-free? In my book,
> they're definitely not pure.
Again, why keep track of this? The things mentioned so far, increased
modularity and ease of debug, aren't anything really substantial, is
it? Besides those depend on so much more anyway.
Also, it isn't as simple as side-effect vs. pure. Because some
side-effects are what you want, and some are harmless.
To me, this seems like yet another theoretical model that is
interesting in its own right, it helps us think and reason, like we
are doing right now, but applied as a rulebook what to do as
a practically working engineer, it'll limit you rather than
enhance you.
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-10-31 18:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 16:50 problems with Emacs 28 Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 17:33 ` Jean Louis
2020-10-23 18:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 1:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 12:56 ` Stefan Monnier
2020-10-24 12:57 ` Stefan Monnier
2020-10-24 9:46 ` Michael Heerdegen
2020-10-24 17:00 ` Drew Adams
2020-10-24 19:26 ` Michael Heerdegen
2020-10-24 22:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 22:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-25 12:13 ` Michael Heerdegen
2020-10-25 14:15 ` Drew Adams
2020-10-27 0:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-27 10:22 ` Michael Heerdegen
2020-10-28 16:21 ` Jens C. Jensen
2020-10-28 17:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-28 17:18 ` Stefan Monnier
2020-10-31 18:26 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-11-01 13:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:16 ` Eli Zaretskii
2020-10-23 18:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 18:44 ` Stefan Monnier
2020-10-24 0:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-23 19:09 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-10-24 0:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=87v9eqntf8.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).