unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [Emacs-diffs] master 37940b3: min and max now return one of their arguments
Date: Tue, 07 Mar 2017 10:04:57 -0500	[thread overview]
Message-ID: <jwvinnlqgew.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <20170307012701.1C05D23F1F@vcs0.savannah.gnu.org> (Paul Eggert's message of "Mon,  6 Mar 2017 20:27:00 -0500 (EST)")

>     min and max now return one of their arguments
    
Since this is an incompatible change, I'm wondering what is the
motivation for this change.  I can see advantages to both behaviors, but
I don't see an overriding advantage that would justify getting over the
inertia and breaking backward compatibility.


        Stefan



       reply	other threads:[~2017-03-07 15:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170307012700.3354.30219@vcs0.savannah.gnu.org>
     [not found] ` <20170307012701.1C05D23F1F@vcs0.savannah.gnu.org>
2017-03-07 15:04   ` Stefan Monnier [this message]
2017-03-08  3:04     ` [Emacs-diffs] master 37940b3: min and max now return one of their arguments John Wiegley
2017-03-08  6:08     ` Paul Eggert
2017-03-08 15:54       ` Eli Zaretskii
2017-03-08 22:04         ` Paul Eggert
2017-03-09 16:10           ` Eli Zaretskii
2017-03-09 16:25             ` Clément Pit-Claudel
2017-03-09 16:54               ` Eli Zaretskii
2017-03-09 17:09                 ` Clément Pit-Claudel
2017-03-09 17:45             ` Paul Eggert
2017-03-09 18:34               ` Eli Zaretskii
2017-03-07 19:08   ` Glenn Morris
2017-03-08  4:26     ` Tino Calancha
2017-03-08  5:27     ` Paul Eggert
2017-03-08  7:54       ` Andreas Schwab
2017-03-08  8:29       ` Andreas Schwab
2017-03-08 18:47         ` Paul Eggert
2017-03-08 22:10           ` Andreas Schwab
2017-03-11 14:46       ` Andreas Politz
2017-03-12  1:46         ` Tino Calancha
2017-03-12 23:33           ` Andreas Politz

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=jwvinnlqgew.fsf-monnier+emacsdiffs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@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).