Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93626 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22231 invoked from network); 29 May 2016 17:54:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 May 2016 17:54:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=colinodell@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=colinodell@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.53 as permitted sender) X-PHP-List-Original-Sender: colinodell@gmail.com X-Host-Fingerprint: 209.85.218.53 mail-oi0-f53.google.com Received: from [209.85.218.53] ([209.85.218.53:33595] helo=mail-oi0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 81/93-23584-9DC2B475 for ; Sun, 29 May 2016 13:54:33 -0400 Received: by mail-oi0-f53.google.com with SMTP id k23so241874415oih.0 for ; Sun, 29 May 2016 10:54:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cZjo/G5Z0HuFsHnbW1p42CgGwfox57QpHYzmu2tor0c=; b=yEo5Ch6tOhu+qhzG1j2xj8/qbCuDu2XKxzZh2+zrScnzx0K693PNYuo/go+u13iTzp T4stUesLqJUOK5Z5q0NPlpk6ChloEzsnmDlFsDjtlg5ecU6HZ5xwbb7vNVJvIC5NDaZ4 BflRQulY0+duExwLNhtrIMGtPtKiJqoAaLXJmCIATH0k0qoLI+z5bg+QRsAbTqNwXN01 X+/G/P78B+mTILm2Wc1U2ReEHDwOF0wkfEepOXkdr5kISB+7WWvcqSQWIniIdCQ9HQ5m qkIxUrjW8KWlJEPr0SPjcHbjawSajJqZ6rnnxHoA3M9Xpi9ALvD4ggO5fprz+/hg8zDP WD4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cZjo/G5Z0HuFsHnbW1p42CgGwfox57QpHYzmu2tor0c=; b=BRfduMmdjanXC8uGiAx8WkCq4CXMeEIfzCbpDF3vb1S04tARjQfv+Gw9ljU87r4yi9 x7M4Dn7cJChEo2rPiqQ9DWtuVitaVOJUOiWCZA25IiTQWtiawfIWgQWGnREW3Oh7Vte3 10a3m2Eli92wWwUyATSFS1n6HokP9C/ohhUlpQmBMfH7AnK68mwMzoPwCUqSDGQl9F5T 1KYlQTTal/qnlqqkBA5rYlnJYaXgQ0fY3XbsXhY/l3O4r3HusdR0ZfVn0yGcUa+RmSgG 29G+PFUPXePIpT1kNgPkE61hTPiaI+x7AYhuJR8miedvwCLWk1iK9LKLN4gdyHDoU3SS 9kJQ== X-Gm-Message-State: ALyK8tJhHKulMYuSOS0159fG6Tw08fzIgRq6YaneQJOBrk58D2lu99gomKTyHK99FMmUWWaBxgEC3xIC2c2KGw== X-Received: by 10.157.8.240 with SMTP id 103mr14268097otf.109.1464544471154; Sun, 29 May 2016 10:54:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 29 May 2016 17:54:21 +0000 Message-ID: To: Andreas Heigl , PHP Internals Cc: jmikola@gmail.com Content-Type: multipart/alternative; boundary=001a113703f0f6079e0533fed4d4 Subject: Re: [PHP-DEV] [RFC Discussion] array_change_keys() From: colinodell@gmail.com ("Colin O'Dell") --001a113703f0f6079e0533fed4d4 Content-Type: text/plain; charset=UTF-8 > > The RFC states "The new array returned by this function will contain the > same values in the same order, but with potentially different keys." > > But further down it states, that on multiple times the same key the last > one will "win". So in that special case it's **not** the same array > anymore. Or did I miss something? > You're right, I didn't word that first part very well. I've revised the RFC to mention the two "exceptions to the rule" earlier. Essentially this function is going to mirror the behavior of array_flip() whenever an invalid or duplicate key is encountered. Thanks for catching that! Colin --001a113703f0f6079e0533fed4d4--