Date: Thu, 26 Aug 2021 07:46:05 -0700
On Thursday, 26 August 2021 06:19:28 PDT Jason McKesson via Std-Proposals
wrote:
> When Thiago asked you to write a proposal, I'm fairly sure he didn't
> mean for you to just take a couple of sentences from this thread and
> throw them into a text file. What we want is something more specific,
> more comprehensive as to the behavior of the feature, and which
> addresses the issues raised in this thread.
To be clear: I agree with Valery that there's a need. I've needed this before;
we use private implementation techniques all the time, with severe hacks to
reduce the number of memory allocations.
I'm not arguing to put a roadblock in the request.
I'm saying that the discussion on the mailing list will not lead to a fruitful
result. Someone needs to take the next step and write a very good paper. And
as any paper that addresses core language changes, it needs to provide
sufficient evidence for why this is a good idea, why the status quo needs to
change (like explaining what hoops developers need to go through), go through
the possible concerns the committee may have, explaining how they're
addressed, and in addition to the recommended syntax, provide alternatives
that were discarded.
I think the CWG has an incubator team that can help you write and improve on
the paper.
wrote:
> When Thiago asked you to write a proposal, I'm fairly sure he didn't
> mean for you to just take a couple of sentences from this thread and
> throw them into a text file. What we want is something more specific,
> more comprehensive as to the behavior of the feature, and which
> addresses the issues raised in this thread.
To be clear: I agree with Valery that there's a need. I've needed this before;
we use private implementation techniques all the time, with severe hacks to
reduce the number of memory allocations.
I'm not arguing to put a roadblock in the request.
I'm saying that the discussion on the mailing list will not lead to a fruitful
result. Someone needs to take the next step and write a very good paper. And
as any paper that addresses core language changes, it needs to provide
sufficient evidence for why this is a good idea, why the status quo needs to
change (like explaining what hoops developers need to go through), go through
the possible concerns the committee may have, explaining how they're
addressed, and in addition to the recommended syntax, provide alternatives
that were discarded.
I think the CWG has an incubator team that can help you write and improve on
the paper.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Received on 2021-08-26 09:46:12