Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

On Tue, Jul 30, 2019 at 10:37 PM Nikita Popov wrote: > Zeev, > > Nikita, Similarly to how I answered Bob, I want to prefix my message with an off-topic statement that I think is important, albeit obvious. I think you're a remarkably talented developer that is an invaluable asset to the PHP proje

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

I believe I addressed most of what you wrote in my reply to Nikita, except for this: On Tue, Jul 30, 2019 at 10:45 PM Dan Ackroyd wrote: > On Tue, 30 Jul 2019 at 20:09, Zeev Suraski wrote: > If they do - it's absolutely their responsibility > > to defend their proposal > > Zeev, this isn't a r

Re: [PHP-DEV] Re: [RFC] Namespace-scoped declares, again

On Tue, Jul 30, 2019 at 4:08 PM Nikita Popov wrote: > Thanks everyone for your responses! > > I think the discussion resolves around two primary concerns, so let me > address them in turn. > > The first is the general approach of using declares as a > language-evolution mechanism. The concern her

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

On Tue, 30 Jul 2019 at 20:01, Stanislav Malyshev wrote: > > If you do not intend to work with others, that's fine, don't - but > then it can not be a part of the community process. At least > if we still want to have a community and not just a bunch > of people committing changes whenever they fee

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

On Wed, 31 Jul 2019 at 09:50, Zeev Suraski wrote: > > This was not a threat of any kind, "If we need to pull rank with group@ here, we will." "I'm confident that if it ever came to that, I'll have the backing of group@, which is why I wrote what I wrote." Those are threats. You were threatenin

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

On Wed, Jul 31, 2019 at 4:31 PM Dan Ackroyd wrote: > On Wed, 31 Jul 2019 at 09:50, Zeev Suraski wrote: > > > > This was not a threat of any kind, > > "If we need to pull rank with group@ here, we will." > > "I'm confident that if it ever came to that, I'll have the backing of > group@, which is

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

threat /THret/ noun: a statement of an intention to inflict pain, injury, damage, or other hostile action on someone in retribution for something done or not done. Anyway, can we vote on this RFC? On Wed, Jul 31, 2019 at 9:54 AM Zeev Suraski wrote: > > On Wed, Jul 31, 2019 at 4:31 PM Dan Ackroyd

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

On Wed, Jul 31, 2019 at 5:09 PM guilhermebla...@gmail.com < guilhermebla...@gmail.com> wrote: > threat /THret/ noun: a statement of an intention to inflict pain, > injury, damage, or other hostile action on someone in retribution for > something done or not done. > Exactly. If making people stic

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

Hi! > This is why trying to force RFC authors to respond to every point is > such a bad idea. You try to absurdize the position by taking it to unreasonable absolute. Nobody asks anybody to respond to literally *every* point, no matter how minor. Responding on major objections, however, is expect

Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax

Hi! > You and Zeev have disagreed with several RFCs that have passed, and > apparently you're perceiving that as "people committing changes > whenever they feel like". Please, for the love of all that is holy, do not try to guess what I think. You are bad at it. I never claimed that, never though

[PHP-DEV] WeakReference: WeakMap / GC callbacks

Hi internals, I'm following up on a message by Andrea Faulds on Feb 4, 2019 : Have you considered adding a WeakMap type as well — a map of (object) > keys to values where the keys are weakly referenced? This is a useful > construct based on weak referen