Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78263 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55493 invoked from network); 23 Oct 2014 08:44:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Oct 2014 08:44:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=dmitry@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dmitry@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.218.44 as permitted sender) X-PHP-List-Original-Sender: dmitry@zend.com X-Host-Fingerprint: 209.85.218.44 mail-oi0-f44.google.com Received: from [209.85.218.44] ([209.85.218.44:58238] helo=mail-oi0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1A/12-41150-5EFB8445 for ; Thu, 23 Oct 2014 04:44:22 -0400 Received: by mail-oi0-f44.google.com with SMTP id x69so391016oia.3 for ; Thu, 23 Oct 2014 01:44:19 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=wuBmZFTy1TKtJN7upPJTh9P21PG9lWkk3mJ6YkdI/A4=; b=nEQrY6ApG/Pm4nyOD0lcS7C67ny5OhuUUZYOeLhNMfuzklp1Zt0keU/7CD+OMkYPTv AW8ghMsqHHxqykbVDDwEwBcFw6OIGpbtwBLmXNaAGSCPto4YvfsxU5M6tYVbCueiHAkA Xz+ybeHuiK1AlUAMAIEwTrTHdFJVgCSvlT4DXd137kU7Ebo3aULN1/K6b1I/Cesiapsf 9T8EghxELlyKc0F5BCH++s36u4VgkODNcVu3NtBFr9CT6ObSFNF77tloThzj8TgSUj59 7yTFjE9ZviOjsvFAYOSXca9xd6ffL3opLCBJqr+S7xJYk0oJpnFUaK+A6ju0JSM8GvkH JeHA== X-Gm-Message-State: ALoCoQkkYWfBJSoxx31DSKhmiWM3thb0fV93bfLdupltPggk8Lrx2hMk4iKXyk4YrnvDUDTEqmsGx1bbMdaFQeINlApL7AB4Zv/MSJowcmdFQs8D9ID5g1D6mS4njSzDnHEDW8hfi5otjqNIFGDxINMFH2ESSiyklQ== MIME-Version: 1.0 X-Received: by 10.60.147.137 with SMTP id tk9mr3040117oeb.5.1414053859318; Thu, 23 Oct 2014 01:44:19 -0700 (PDT) Received: by 10.60.70.41 with HTTP; Thu, 23 Oct 2014 01:44:19 -0700 (PDT) In-Reply-To: <1414051917.2624.35.camel@localhost.localdomain> References: <1413875212.2624.3.camel@localhost.localdomain> <54469840.3070708@sugarcrm.com> <1414051917.2624.35.camel@localhost.localdomain> Date: Thu, 23 Oct 2014 12:44:19 +0400 Message-ID: To: Joe Watkins Cc: Stas Malyshev , Philip Hofstetter , PHP Internals Content-Type: multipart/alternative; boundary=047d7b3a80eefa7a26050613111f Subject: Re: [PHP-DEV] [RFC] UString From: dmitry@zend.com (Dmitry Stogov) --047d7b3a80eefa7a26050613111f Content-Type: text/plain; charset=UTF-8 this won't completely solve the problem, because array keys won't be UString anymore. Thanks. Dmtiry. On Thu, Oct 23, 2014 at 12:11 PM, Joe Watkins wrote: > On Tue, 2014-10-21 at 10:30 -0700, Stas Malyshev wrote: > > Hi! > > > > > I wish there was a way for specific objects to opt into this. > > > > There will be, if __hashKey() or whatever would be the properly > > bikeshedded name, becomes reality as discussed elsewhere. It shouldn't > > be hard to do and it's exactly what many other languages do when trying > > to use objects as keys for maps. > > > > > > Not ready for discussion yet ... > > https://wiki.php.net/rfc/hashkey > > But it exists, I think it solves a problem for ustring in particular but > it solves the problem in general too. No time to write about it or > discuss it at this moment, but in pipeline, hopefully ... > > Cheers > Joe > > --047d7b3a80eefa7a26050613111f--