From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eric Abrahamsen <eric@ericabrahamsen.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 17:23:16 -0500 [thread overview]
Message-ID: <CAM-tV-8fHDv69Pf93VLOxnWHhXhoWsDHD-VmS2gJwU-pUgC5tg@mail.gmail.com> (raw)
In-Reply-To: <87bmi1nzcq.fsf@ericabrahamsen.net>
On Wed, Jan 10, 2018 at 5:05 PM, Eric Abrahamsen
<eric@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
next prev parent reply other threads:[~2018-01-10 22:23 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 [this message]
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
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
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=CAM-tV-8fHDv69Pf93VLOxnWHhXhoWsDHD-VmS2gJwU-pUgC5tg@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=30039@debbugs.gnu.org \
--cc=damien@cassou.me \
--cc=eric@ericabrahamsen.net \
--cc=nicolas@petton.fr \
/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).