On Friday, 23 August 2024 at 23:55, Rob Landers <rob@bottled.codes> wrote:

> On Fri, Aug 23, 2024, at 23:06, Larry Garfield wrote:

>> With generics, the syntax isn't the hard part. The hard part is type 
>> inference, or accepting that generic-using code will just be extraordinarily 
>> verbose and clumsy. There is (as I understand from Arnaud, who again can 
>> correct me if I'm wrong) not a huge amount of difference in effort between 
>> supporting only Foo<Bar> and supporting Foo<Bar<Baz>>. The nesting isn't the 
>> hard part. The hard part is not having to type Foo<Bar> 4 times across 2 
>> files every time you do something with generics. If that can be resolved 
>> satisfactorily (and performantly), then the road map to reified generics is 
>> reasonably visible.
>
> Ok. But wasn't there something about nesting causing super-linear performance 
> issues? So, disable nesting and don't worry about inference.
> [...]
> Ah, this is what I was thinking of. Thank you. Yeah, instead of "nesting" 
> prior, I was referring to union types.

Rob, with all the kindness I can give, please condense your emails to have a 
semblance of sense.
This is not a bar where you are having a one on one conversation.
You are sending emails to thousands of people on a mailing list that can read 
you.
It would be appreciated if you could go over everything you read, digest the 
content, and then form a reply.
Or at the minimum, if you realize that a previous remark you made does not 
apply, redraft the email.
And possibly even sit on it for a bit before sending it, as you routinely come 
up with a point you forgot to include in your email.

Reading the mailing list is an exhausting task, especially when the volume is 
excessive.
As a reminder to everyone, we have rules: 
https://github.com/php/php-src/blob/master/docs/mailinglist-rules.md

However, in your case, please note the following rule:

> If you notice that your posting ratio is much higher than that of other 
> people, double-check the above rules. Try to wait a bit longer before sending 
> your replies to give other people more time to digest your answers and more 
> importantly give you the opportunity to make sure that you aggregate your 
> current position into a single mail instead of multiple ones.

For the past 2–3 months, you have sent the vast majority of emails on this 
list, this is not what I would consider normal nor expected for your level of 
"seniority" (for the lack of better word) on the project.
This is not to say to stop posting and replying, just to do it in a more 
conscious manner for the rest of us reading you.

Best regards,
Gina P. Banyard

>

Reply via email to