From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Damien Cassou <damien@cassou.me>,
30039@debbugs.gnu.org, Nicolas Petton <nicolas@petton.fr>
Subject: bug#30039: 26.0.90; [26.1] Making my code warning free is impossible with when-let
Date: Wed, 10 Jan 2018 16:03:45 -0800 [thread overview]
Message-ID: <87efmxmfby.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <CAM-tV-9_bRNMQjYqWVTPWaYNajSB9gX0+gZhmsQV2mUWiL4FXg@mail.gmail.com> (Noam Postavsky's message of "Wed, 10 Jan 2018 18:06:20 -0500")
On 01/10/18 18:06 PM, Noam Postavsky wrote:
> On Wed, Jan 10, 2018 at 5:57 PM, Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>
>> Right, and the issue wasn't the introduction of when-let*, it was the
>> very short life-cycle of when-let.
>
> I don't understand how that leads to this:
>
> I have to choose between compiler warnings on the one hand,
> or multiple users running an Emacs without the function, on the other.
>
> Supposing when-let* was only introduced as a replacement to when-let
> in Emacs 30, you would still have to choose between users of Emacs 29
> reporting errors, or get deprecation warnings when compiling in Emacs
> 30. The (hypothetical) longer non-deprecated existence of when-let
> over versions 26,27,28,29 wouldn't help (unless you plan to stop
> developing your package before Emacs 30, I guess).
Ah, you're right. I guess it's just a matter of what Nicolas
mentioned -- these are awfully handy macros, and we're adopting them
early.
next prev parent reply other threads:[~2018-01-11 0:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 7:27 bug#30039: 26.0.90; [26.1] Making my code warning free is impossible with when-let Damien Cassou
2018-01-09 8:16 ` Nicolas Petton
2018-01-10 19:11 ` Noam Postavsky
2018-01-10 21:50 ` Nicolas Petton
2018-01-11 9:19 ` Damien Cassou
2018-01-19 20:00 ` Noam Postavsky
2018-01-19 20:26 ` Eli Zaretskii
2018-01-19 20:40 ` Noam Postavsky
2018-01-20 7:42 ` Eli Zaretskii
2018-01-09 14:05 ` Noam Postavsky
2018-01-09 14:23 ` Damien Cassou
2018-01-09 14:43 ` Noam Postavsky
2018-01-10 12:13 ` Damien Cassou
2018-01-10 15:45 ` Eli Zaretskii
2018-01-10 16:24 ` Nicolas Petton
2018-01-10 17:24 ` Glenn Morris
2018-01-10 18:46 ` Eli Zaretskii
2018-01-10 21:48 ` Nicolas Petton
2018-01-10 22:05 ` Eric Abrahamsen
2018-01-10 22:23 ` Noam Postavsky
2018-01-10 22:40 ` Nicolas Petton
2018-01-10 22:57 ` Eric Abrahamsen
2018-01-10 23:06 ` Noam Postavsky
2018-01-11 0:03 ` Eric Abrahamsen [this message]
2018-01-11 9:02 ` Nicolas Petton
2018-04-14 20:17 ` Lars Ingebrigtsen
2018-04-15 11:53 ` Michael Heerdegen
2018-02-21 22:28 ` Michael Heerdegen
2018-02-22 7:42 ` Damien Cassou
2018-03-06 15:12 ` 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=87efmxmfby.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=30039@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=nicolas@petton.fr \
--cc=npostavs@users.sourceforge.net \
/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.