GNU bug report logs - #30039
26.0.90; [26.1] Making my code warning free is impossible with when-let

Previous Next

Full log

View this message in rfc822 format

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Eric Abrahamsen <eric <at> ericabrahamsen.net>
Cc: Damien Cassou <damien <at> cassou.me>, 30039 <at> debbugs.gnu.org, Nicolas Petton <nicolas <at> petton.fr>, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#30039: 26.0.90; [26.1] Making my code warning free is impossible with when-let
Date: Wed, 10 Jan 2018 17:23:16 -0500

On Wed, Jan 10, 2018 at 5:05 PM, Eric Abrahamsen
<eric <at> ericabrahamsen.net> wrote:
> I've encountered no other
> functions where the introduction-deprecation-removal cycle has been so
> tight that I have to choose between compiler warnings on the one hand,
> or multiple users running an Emacs without the function, on the other.

Isn't it standard Emacs practice to mark a function deprecated in the
same commit which introduces the replacement? Examples:

[1: 6f1dea5]: 2017-10-18 18:43:44 -0700
  Spelling fixes
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=6f1dea5c74057707bf367f863a8be5750bbb6094

[2: 91932ff]: 2017-02-23 22:39:53 -0500
  Use cl-print for Edebug and EIEIO
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=91932fff1ded8ed3b4d39dd06891f26960153b9e

[3: 3db521c]: 2016-06-07 21:34:51 -0400
  Reduce allout.el's pollution of the namespace.
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=3db521ccaf3a5b6892bf23ea1305c7cfe9aa1cce

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.