From: akater <nuclearspace@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Some improvements for cl-flet
Date: Thu, 07 Oct 2021 02:32:15 +0000 [thread overview]
Message-ID: <87sfxdr2ds.fsf@gmail.com> (raw)
In-Reply-To: <87y281cowz.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
I must leave one more notice.
What will the following forms return, with cl-flet being implemented as is?
(let ((n 0))
(cl-symbol-macrolet ((f0 (progn (cl-incf n) #'identity)))
(cl-flet ((f f0))
(f t) (f t)
n)))
(let ((n 0))
(cl-symbol-macrolet ((f0 (progn (cl-incf n) #'identity)))
(cl-flet ((f (identity f0)))
(f t) (f t)
n)))
Turns out, the value is not determined by cl-flet spec but rather by its implementation. If it is optimized in a certain way (which is the case right now), the values will diverge.
While of course they shouldn't.
> Personally I wouldn't mind when this functionality would be provided by
> some other form, but there is backward compatibility.
>
> Don't you think that cl-lib (see Stefan's answer) differs from CL
> much more in other aspects?
No. The note was about cl- prefix. I can often write CL code easily
portable to Elisp and back again by merely writing cl: prefixes in it.
Of course, even without them, porting is trivial. The ability to share
code is beneficial. I think we should aim to eliminate the difference
between cl-lib and CL rather than extend it.
> I see your point. OTOH, removing the expression syntax case would be a
> backward incompatible change potentially break existing code - right?
Introducing it potentially broke existing code in the first place.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2021-10-07 2:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 12:51 Some improvements for cl-flet akater
2021-09-11 23:32 ` Michael Heerdegen
2021-09-12 3:35 ` akater
2021-09-12 15:38 ` Stefan Monnier
2021-09-13 0:14 ` Michael Heerdegen
2021-09-13 2:26 ` Stefan Monnier
2021-10-07 2:32 ` akater [this message]
2021-10-07 18:03 ` Stefan Monnier
2021-10-08 21:57 ` Richard Stallman
2021-10-09 5:23 ` akater
2021-10-09 6:01 ` Michael Heerdegen
2021-10-09 23:37 ` Richard Stallman
2021-10-10 10:41 ` Po Lu
2021-10-10 20:27 ` João Távora
2021-10-10 21:57 ` Stefan Monnier
2021-10-11 0:45 ` [External] : " Drew Adams
2021-10-11 21:16 ` Richard Stallman
2021-10-11 21:26 ` João Távora
2021-10-12 22:42 ` Richard Stallman
2021-10-12 0:05 ` Po Lu
2021-10-12 0:29 ` Robin Tarsiger
2021-10-12 22:43 ` Richard Stallman
2021-10-09 23:33 ` Richard Stallman
2021-10-09 23:33 ` Richard Stallman
2021-10-14 4:00 ` Michael Heerdegen
2021-09-23 22:37 ` [PATCH] " akater
2021-09-23 22:41 ` akater
2021-09-24 7:11 ` João Távora
2021-09-24 15:20 ` [PATCH] Some improvements for cl-flet, and some more akater
2021-09-24 16:22 ` João Távora
2021-09-25 1:28 ` Lars Ingebrigtsen
2021-09-25 8:37 ` João Távora
2021-09-24 20:30 ` [PATCH] Some improvements for cl-flet akater
2021-09-26 6:54 ` Lars Ingebrigtsen
2021-09-26 12:04 ` akater
2021-09-26 12:36 ` Lars Ingebrigtsen
2021-10-03 3:51 ` Stefan Monnier
2021-10-07 5:02 ` akater
2021-10-07 18:23 ` Stefan Monnier
2021-11-03 12:59 ` akater
2021-11-09 20:37 ` Stefan Monnier
2021-10-09 5:33 ` akater
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=87sfxdr2ds.fsf@gmail.com \
--to=nuclearspace@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--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).