Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110197
To: algerdblr@gmail.com
References: <ce6a438b-9473-9b10-5475-a9a0f3deb72d@gmail.com>
Cc: internals@lists.php.net
Message-ID: <910b8634-388a-8f54-3fed-5392e688e0f7@gmail.com>
Date: Sun, 17 May 2020 16:48:16 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <ce6a438b-9473-9b10-5475-a9a0f3deb72d@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------08BB6927553B002F02B51972"
Content-Language: en-US
Subject: Re: [RFC] Guard statement
From: algerd.blr@gmail.com (Pavel Patapau)

--------------08BB6927553B002F02B51972
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Thank you everyone for responses.

I've received huge amount of constructive criticism and useful feedback 
from various sources and after evaluation I've decided to withdrawn this 
RFC.

On 5/16/20 12:13 PM, Pavel Patapau wrote:
>
> Hello everyone,
>
> I want to propose new syntax addition - guard statement, that executes 
> code only if expression equals false and must contain control-flow 
> changing code, and written a respective RFC:
>
> https://wiki.php.net/rfc/guard_statement
> <https://wiki.php.net/rfc/unbundle_xmlprc>
>
> Implementation in progress.
>
> I started work before this proposal 
> https://externals.io/message/110107 and respected some moments in the RFC.
>
>
> Thanks for consideration,
> Pavel
>
>
>

--------------08BB6927553B002F02B51972--