Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108859 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 57360 invoked from network); 5 Mar 2020 01:17:22 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 5 Mar 2020 01:17:22 -0000 To: internals@lists.php.net References: Date: Thu, 5 Mar 2020 00:36:54 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Posted-By: 46.59.72.204 Subject: Re: [PHP-DEV] Make sorting stable From: ajf@ajf.me (Andrea Faulds) Message-ID: Christoph M. Becker wrote: > Given that we have internal classes which deliberately have such > comparison behavior (i.e. returning 0 or 1, to signal that there is no > order defined), e.g. Closures[1], I tend to prefer raising a warning > instead of trying to recover. Oof… I wonder if we should make FALSE (maybe NULL too?) a special value to signify “no ordering”? Thanks, Andrea