Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109402 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 87565 invoked from network); 28 Mar 2020 22:35:27 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Mar 2020 22:35:27 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 9F0F41804D8 for ; Sat, 28 Mar 2020 14:00:55 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-wm1-f52.google.com (mail-wm1-f52.google.com [209.85.128.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 28 Mar 2020 14:00:55 -0700 (PDT) Received: by mail-wm1-f52.google.com with SMTP id b12so15438626wmj.3 for ; Sat, 28 Mar 2020 14:00:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=uIHj0K9EExpE4uo9IWNMHPaV4MlAYl3BQh1weRiL1Nc=; b=QUNsn8NDguZj0732CvhZ5brxv9KXdp8TgJiA1t5wjhA/m4rftWX/IV0iDrA3K6tkjs YZmWn3+tq6rs+pUlWzV8h3qjm5NpnPABT9C6PYegxUL1n0hn+RBIzkONRs2II6zda+t0 do4vU1g24zY6eD12Y4jVKNfTIPhs8MhFvgsxc4XL5gQG6c8NlX8XJVQ1mpg+BR666APR 4DNFrL8lnryq7/xTLE9NF0+U/k1HrdmyHXBuHo0sFB2nB7sjDfy/TzVqxvYWfD9IQ9K1 gIYmqVFZ2AH8P8Q/sw5xkyqjngmJcj0cxjxFuERRCRd1j4U0sq5WgIOAUXq415t6XL0T 1UlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=uIHj0K9EExpE4uo9IWNMHPaV4MlAYl3BQh1weRiL1Nc=; b=Cs3tlcKN1j5ME38IXDzkD/R2GoUI9cOxS7gE8YU1AJ7d1hOFkeighV9l3poeTtMO1x sls3h40osj3MWRPrfudNQ2Bzi9zqs7V3MCvhkqIe8sIb3J5JUnFS33NM42KeT39fPhhC NbOff3R1Gdm/Biklf0mgGUXP29vDZpknTjGsKa8qU99vTgVeXmM89utyYSe1MrM25b2G GnC6dcMIwC+637wCSp0mLrUJdB2jyrmHJ2iPJmocUIcKU8s0eNfuAhKWCzORufd2edpS wQ2vUY7xWfknZVvO8bEV95Cu7b/cKM5YjMv5E7FcpKF6R1OLytFpimk4tcBjvOryR1qK N9Og== X-Gm-Message-State: ANhLgQ3SAUXasN0MV0j9RSfmkukTrBGf3CasHnLQ2Fs18c+zljd2KXWv CT7/aAnc3FNTzS3ccA+Mcc7nRiVL X-Google-Smtp-Source: ADFU+vvNNSDNuW63mVmI4JloeCZ62zVqLJpyzXEe3IwHxvs55SDzG1EUhNOmqd5Bw7s85bKxu3iKqg== X-Received: by 2002:a1c:2b43:: with SMTP id r64mr5363318wmr.77.1585429252900; Sat, 28 Mar 2020 14:00:52 -0700 (PDT) Received: from [192.168.0.14] (cpc84253-brig22-2-0-cust114.3-3.cable.virginm.net. [81.108.141.115]) by smtp.googlemail.com with ESMTPSA id u22sm2815030wmu.43.2020.03.28.14.00.51 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 28 Mar 2020 14:00:51 -0700 (PDT) To: internals@lists.php.net References: Message-ID: Date: Sat, 28 Mar 2020 21:00:48 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB Subject: Re: [PHP-DEV] [RFC] Allow trailing comma in parameter lists From: rowan.collins@gmail.com (Rowan Tommins) On 26/03/2020 18:52, Nikita Popov wrote: > Hi internals, > > This has been declined in the past, but I just keep making this mistake, > and believe it deserves reconsideration... > > https://wiki.php.net/rfc/trailing_comma_in_parameter_list > > Nikita > Hi Nikita, While I'd personally be fine with this change, I think we should understand why the previous proposal failed rather than just hoping the vote goes differently this time. Specifically, this vote was only 3 years ago, and although it achieved a majority, was well short of the 2/3 requirement: https://wiki.php.net/rfc/list-syntax-trailing-commas#functionmethod_arguments_declarations_calls Notably, a followup RFC proposing only function *calls* allow trailing commas, passed a few months later, and includes this specific rationale: https://wiki.php.net/rfc/trailing-comma-function-calls#wait_didn_t_we_just_vote_on_this > I was contacted by many “no” voters saying that they would have voted “yes” for function calls, but “no” for function declarations. ThisRFC proposes allowing a trailing comma in function call syntax only. Looking back at the discussions from 2017, I can see a couple of people taking that position, but not expanding on it. Does anyone still hold that view, and want to explain why they feel that way? Side-note - here's a quick timeline of related RFCs: - Feb 2013: https://wiki.php.net/rfc/trailing-comma-function-args - function calls only, rejected 15:20 - Oct 2015: https://wiki.php.net/rfc/revisit-trailing-comma-function-args - withdrawn in favour of next RFC - Nov 2015, voted Jan 2017: https://wiki.php.net/rfc/list-syntax-trailing-commas - function calls and parameters, rejected 24:20 - Oct 2017: https://wiki.php.net/rfc/trailing-comma-function-calls - function calls only, passed 30:10 - Mar 2020: https://wiki.php.net/rfc/trailing_comma_in_parameter_list - function parameters only... Regards, -- Rowan Tommins (né Collins) [IMSoP]