On Wed, Sep 18, 2019 at 6:32 PM guilhermebla...@gmail.com < guilhermebla...@gmail.com> wrote:
> Nikita, > > I'd suggest to wait until the current vote ends and then open a new > RFC to vote this one, otherwise it'll be disrupting. > Err, to be clear, I'm not suggesting to change the RFC under vote. We have enough drama without that ;) I certainly don't care about this enough to run it through a separate RFC vote either. I'd like a simple consensus decision on a minor point. If Chase & co tell me that "This is no problem for us, go ahead" or "This is going to break all our code, leave it alone" that's good enough for me. Context is that the current notice prevents constant propagation optimizations. A warning won't help us either, but it would be the first step towards making it an exception in the future, which *would* enable those optimizations. Regards, Nikita > > On Wed, Sep 18, 2019 at 12:29 PM Nikita Popov <nikita....@gmail.com> > wrote: > > > > On Thu, Sep 12, 2019 at 2:17 PM Nikita Popov <nikita....@gmail.com> > wrote: > > > > > Hi internals, > > > > > > I've opened the vote on //wiki.php.net/rfc/engine_warnings. > > > > > > There are 4 votes, all of them independent. The first 3 are for > specific > > > cases that were controversial during the discussion, the last one is > for > > > the remainder of the proposal. > > > > > > Voting closes 2019-09-26. > > > > > > Regards, > > > Nikita > > > > > > > I just realized that I missed one notice here, because it is generated > from > > a different location: "Constant %s already defined" (The define/const > will > > be ignored and the previous value used.) > > > > It would be great to have that as an exception for optimization reasons, > > but as it's only a notice right now ... what do people think about > > promoting it to a warning? > > > > Nikita > > > > -- > Guilherme Blanco > SVP Technology at Statflo Inc. > Mobile: +1 647 232 5599 >
