Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80239
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.41 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
In-Reply-To: <CAEZPtU4LP7hfjYNf1XaExPwu8yd4XH3jPOK5rbjG=qggjrfh=g@mail.gmail.com>
Date: Tue, 6 Jan 2015 16:14:25 +0100
Cc: Xinchen Hui <laruence@php.net>,
 PHP Internals <internals@lists.php.net>,
 Dmitry Stogov <dmitry@zend.com>,
 Nikita Popov <nikita.ppv@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-ID: <24E2F76C-50D8-40CC-B871-BA0CDFBCBCBB@heroku.com>
References: <CABBJUpcxizh-SMQNOYX4Ejr6sOnoGw-78Nz28Db4JKWwNd9XCw@mail.gmail.com> <CAEZPtU4LP7hfjYNf1XaExPwu8yd4XH3jPOK5rbjG=qggjrfh=g@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Subject: Re: [PHP-DEV] Faster zend sorting implementation
From: dz@heroku.com (David Zuelke)

On 06.01.2015, at 05:42, Pierre Joye <pierre.php@gmail.com> wrote:

> I am not sure about that. Introducing a not easy to catch BC break for
> 0.1% gain on function (or even for the whole app) is not very
> appealing.
>=20
> However, there is nothing in the documentation actually describing how
> it works and there are clear warnings about the unpredictable results.
> That means we won't actually break it,per definition. I only wonder if
> it is worth the effort for such little gain (yes, the ocean is made of
> drops ;).

The clear benefit I see is that it turns it into a stable sort, although =
we could of course always break that again in the future unless we =
explicitly specify/guarantee it to be stable from now on (without any =
other guarantees about the algorithm).