Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109537 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 12555 invoked from network); 5 Apr 2020 13:58:25 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 5 Apr 2020 13:58:25 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8A8511804B8 for ; Sun, 5 Apr 2020 05:25:50 -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=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE 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-vk1-f177.google.com (mail-vk1-f177.google.com [209.85.221.177]) (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 ; Sun, 5 Apr 2020 05:25:49 -0700 (PDT) Received: by mail-vk1-f177.google.com with SMTP id p123so3237682vkg.1 for ; Sun, 05 Apr 2020 05:25:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xIwrlpD4DUcd5rQEpoEuISlXq7o0tLg4AZhQB0cPT7A=; b=1lW4JJ/DH/25KgbWhBqIAGd3VUfKVNkxj/TT+ehpmjrqkh/fpAAMiVnbuo87yydF8f Aos0RrRfesCGSCUW+d19tieBxi2OH2Tj4cIB1BDba2UHh0T2f6ROyJcNTab5Y2y/uq10 8HhoZMr7aLOzhNQv80tnL+8r0lGp0e2WwFcBxdmTnNEOJgV+XP92QQQiBU0ET5EdbFY9 F6tgqDdXBI/jOLlogkaEkJ/vTfnUfdd2Yyzl/YH9TOBI2Er/5SppsuZYM+sMMmaavGOK h/Fvduhbj5mIvIoNj58uxVI79UnCfjaZKkdQJswLklNTIKD17iqtGddC3Ax/SsDwRBys G8iQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xIwrlpD4DUcd5rQEpoEuISlXq7o0tLg4AZhQB0cPT7A=; b=cweVwh80ex86WXNxY+Eyk54dotGCLaRfKn5NE3KmDzrw/Dy2iSnH4qIec6l5gOs3E9 DzlmxDIM75Ti+9d3xHuOIUPE7I5bOEo5BnBODlbaIpKD+ghh/ndnlvvv3DNsOu+rQkb1 +yOZeBBfnXriKSHc8aXzKuVz2uZ9bI3n03Pcj1s3CrrBUMkYIuCNWEtoNK31agBY1Bp8 oxUxI+O+eiWYRpGU4GT2IIyq2VzOWDZmmxIHB1/VOAtE95LY1DkRErAtLJc/jY/5Yekx tYyNtTNwHUBSX55X/Dkam8KO0daofLLe07Li3Wg1l3e0jMW0KdsvPaNWyAHqG0WjDh0H 2KCA== X-Gm-Message-State: AGi0PubIpUoXTuF4xNJeeKllg/o0fKudEm9HXzmJ7XkBPw4ozAHTmA/q kFNt/dtqgSRCsPKCFDbb1+t5I2hNAdPbFguxDXaqkw== X-Google-Smtp-Source: APiQypKNhZ8W24VI8dD16Ay2jdCXCCGV4HKkAdb4HPZK/CpLwVKipdvCau7kiOjhy7Rhg6kbCPUAcKPtFLEwJGYCkBw= X-Received: by 2002:a1f:200c:: with SMTP id g12mr11321228vkg.84.1586089546925; Sun, 05 Apr 2020 05:25:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 5 Apr 2020 13:25:36 +0100 Message-ID: To: Ilija Tovilo Cc: PHP internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [VOTE] throw expression From: Danack@basereality.com (Dan Ackroyd) On Sun, 5 Apr 2020 at 13:05, Ilija Tovilo wrote: > > "What are the rules here, can" "... the rules are more what you'd call "guidelines" than actual rules." As a project we should clarify exactly what is meant to happen when issues are found in an RFC that affect how people are going to vote. But for this case; there is plenty of time until the deadline for RFCs that target PHP 8. As it's a small but non-trivial change, I'd recommend closing the vote, updating the RFC to either have the correct behaviour around precedence, or if it's not possible to do that, disallow code that has the ambiguous/surprising behaviour. Having what people are voting on change, when votes are currently being cast is a thing that leads to drama. Once that issue is fixed, then wait two weeks and put the RFC to a vote and it should sail through imo. > yours was literally the only criticism I received. In an attempt to set expectations; if a point is already being addressed as part of the discussion, it's unlikely that other people are going to "+1" that*. Extra email messages take up people's time and don't add much value. Currently it's the responsibility of the RFC author to make sure all points are addressed. Arguably that's something that could be split off to be a role done by someone else. cheers Dan Ack * moving to a discussion platform that did allow indicating agreement with an argument in a way that didn't take up people's time would be nice...