Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80345 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21315 invoked from network); 11 Jan 2015 03:00:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jan 2015 03:00:35 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.216.170 mail-qc0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:56428] helo=mail-qc0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 65/9A-48183-257E1B45 for ; Sat, 10 Jan 2015 22:00:34 -0500 Received: by mail-qc0-f170.google.com with SMTP id x3so14218688qcv.1 for ; Sat, 10 Jan 2015 19:00:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=TvrFkvL3vUjrbhQcCSIZEG59lsyHNaMj7uMALnHkGcY=; b=CSz6KA2Ys6KqpunQi7PwM0ikunLxDN4dipcXRNLAFzEptOyXD0ig84Kxl6JbXS9Jcl oYGPz6XSr7KqPdCdFG213ACoxnBlb1WOSZg4SD9PMRUO2lPbsW79lOZmvM0jfs+60ds+ dqJ0zP5By5ga/Oy2ass64/E+4DEXA9XaJtAJhJRm/BfDqhvsbpqgUSZ+l19ZBolakja3 ruIx/HtuJXVSBVMqntY9QlE7B9VdZTAxMPBdF6d9aFrJeL1rg3jmG0/1BtMz36d8E8Bu +eBIOMBjd3BFqRmGs20WSDixbo33BVjFDes3o9fNuP1Y9wxQObobUr6l/I/PD1NmQPtA yBJA== X-Received: by 10.140.90.112 with SMTP id w103mr36742775qgd.65.1420945230993; Sat, 10 Jan 2015 19:00:30 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.93.70 with HTTP; Sat, 10 Jan 2015 18:59:50 -0800 (PST) In-Reply-To: <24E2F76C-50D8-40CC-B871-BA0CDFBCBCBB@heroku.com> References: <24E2F76C-50D8-40CC-B871-BA0CDFBCBCBB@heroku.com> Date: Sun, 11 Jan 2015 11:59:50 +0900 X-Google-Sender-Auth: eaP4D6Zx6OQyLfyMb_pnOhUnwss Message-ID: To: David Zuelke Cc: Pierre Joye , Xinchen Hui , PHP Internals , Dmitry Stogov , Nikita Popov Content-Type: multipart/alternative; boundary=001a11c11a98bd22f5050c5797a7 Subject: Re: [PHP-DEV] Faster zend sorting implementation From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c11a98bd22f5050c5797a7 Content-Type: text/plain; charset=UTF-8 Hi all, On Wed, Jan 7, 2015 at 12:14 AM, David Zuelke 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. > > > > 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). Stable sort is more intuitive than unstable sort. Since stable sort is a little faster than current, the only issue would be "whether we will make it a feature or not". This might be a good theme for RFC in the future. (Just merge the patch and decide later.) Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c11a98bd22f5050c5797a7--