Re: Re: [RFC][VOTE] E_WARNING on invalid container read-adccess

From: Date: Thu, 01 Sep 2016 00:18:07 +0000
Subject: Re: Re: [RFC][VOTE] E_WARNING on invalid container read-adccess
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-95527@lists.php.net to get a copy of this message
> On Wed, Aug 31, 2016 at 7:49 AM David Walker <dave@mudsite.com> wrote: > Hi all, > > As of now, the scheduled time the vote is to close, the RFC stands 19-4 > (accepted). Given this is my first solo RFC, I'm not really sure protocol > to go from here. Dmitry does raise that the implementation I put forward > maybe a bit hackish compared to what someone much more knowledgeable could > implement. So I'm not certain if the RFC should be deemed accepted, or, > fall into the howto section 7(3) and go back to discussion (if it is > considered a serious issue). > > Direction appreciated. The idea is approved. It still has to be an accepted PR. So, take the dissenting feedback as a guide to improve the test coverage and implementation. Possibly try the null coalesce approach as an alternative implementation: that might make it all simpler! If you get stuck, bounce the list a question. We're here to help.

« previous php.internals (#95527) next »