From: Mike Woolley <mike@bulsara.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 39919@debbugs.gnu.org, 31232@debbugs.gnu.org, rms@gnu.org
Subject: bug#31232: bug#39919: 26.3; Incorrect byte-compiler warning
Date: Tue, 28 Apr 2020 19:48:49 +0100 [thread overview]
Message-ID: <3855CC4F-D09F-4E0B-B746-1909C9FA0583@bulsara.com> (raw)
In-Reply-To: <87wo5z5vqs.fsf@web.de>
Thanks for the explanation Michael.
How about changing dotimes as you suggested, but making cl-dotimes have it’s own implementation with the result parameter fix applied?
Then everyone’s a winner - those who want the CL behaviour can have it, but core Emacs will have a cleaner version.
Thanks,
Mike
> On 28 Apr 2020, at 19:13, Michael Heerdegen <michael_heerdegen@web.de> wrote:
>
> Mike Woolley <mike@bulsara.com> writes:
>
>> I think people using `dotimes' from `cl’ are going to expect it to
>> work like in Common Lisp (as that’s the whole point).
>
> But note that dotimes is in subr.el, and cl-dotimes is separate (though
> it's currently implemented on top of dotimes).
>
>> Just deprecating the result parameter because it’s too hard doesn’t
>> seem like a good solution :-)
>
> I regret that I said it like that, no, that's not a reason. The main
> reason is that the whole existence (usefulness) of the RESULT argument
> and its position in the syntax are questionable.
>
> Michael.
>
next prev parent reply other threads:[~2020-04-28 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 23:18 bug#39919: 26.3; Incorrect byte-compiler warning Mike Woolley
2020-03-05 13:50 ` Michael Heerdegen
2020-03-05 14:01 ` Mike Woolley
2020-03-05 14:18 ` Michael Heerdegen
2020-03-05 22:20 ` Michael Heerdegen
2020-03-07 4:23 ` Richard Stallman
2020-03-07 12:52 ` Mike Woolley
2020-04-28 2:52 ` Michael Heerdegen
2020-04-28 16:35 ` Mike Woolley
2020-04-28 18:08 ` bug#31232: " Michael Heerdegen
2020-04-28 18:48 ` Mike Woolley [this message]
2020-04-28 20:14 ` Michael Heerdegen
2020-03-08 0:49 ` Michael Heerdegen
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=3855CC4F-D09F-4E0B-B746-1909C9FA0583@bulsara.com \
--to=mike@bulsara.com \
--cc=31232@debbugs.gnu.org \
--cc=39919@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=rms@gnu.org \
/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).