all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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#39919: 26.3; Incorrect byte-compiler warning
Date: Tue, 28 Apr 2020 17:35:47 +0100	[thread overview]
Message-ID: <5F5C5856-EBFE-4359-91CB-1FE592865B23@bulsara.com> (raw)
In-Reply-To: <877dy07253.fsf@web.de>

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

I think people using `dotimes' from `cl’ are going to expect it to work like in Common Lisp (as that’s the whole point).

Just deprecating the result parameter because it’s too hard doesn’t seem like a good solution :-)

Thanks,
Mike

> On 28 Apr 2020, at 03:52, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> 
> Mike Woolley <mike@bulsara.com> writes:
> 
>> Yes that fixes the issue in the test cases I sent.
>> Also looks good in my real code where I noticed the problem!
> 
> Seems the current warning is a compromise.  It is not perfect because it
> is not really clear what the warning means.  I would vote for a clear
> "argument is deprecated" warning.
> 
> Michael.


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

  reply	other threads:[~2020-04-28 16:35 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 [this message]
2020-04-28 18:08                 ` bug#31232: " Michael Heerdegen
2020-04-28 18:48                   ` Mike Woolley
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5F5C5856-EBFE-4359-91CB-1FE592865B23@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.