Date: Wed, 12 May 2021 12:43:16 -0500
On Wed, May 12, 2021 at 9:57 AM charleyb123 via SG14 <sg14_at_[hidden]>
wrote:
> * Prefer APIs that accept memory as-passed-in by the caller, rather than
> rely upon internal allocation semantics, or reliance upon allocators.
>
> By defining APIs that demanded already-allocated-memory as parameters, we
> could:
>
Some concrete steps that someone could start on immediately:
1. Survey std:: for APIs that could be enhanced with that aim. And write a
paper about it.
2. Research if making the APIs accept&use a PMR is sufficient. Or if some
alternate method is needed. And what would that alternate method be? And
write a paper about it.
3. Eventually, design API alternatives for existing std functionality that
take (1) and (2) into account. And write a paper about it, hopefully with a
prototype implementation with measurements.
wrote:
> * Prefer APIs that accept memory as-passed-in by the caller, rather than
> rely upon internal allocation semantics, or reliance upon allocators.
>
> By defining APIs that demanded already-allocated-memory as parameters, we
> could:
>
Some concrete steps that someone could start on immediately:
1. Survey std:: for APIs that could be enhanced with that aim. And write a
paper about it.
2. Research if making the APIs accept&use a PMR is sufficient. Or if some
alternate method is needed. And what would that alternate method be? And
write a paper about it.
3. Eventually, design API alternatives for existing std functionality that
take (1) and (2) into account. And write a paper about it, hopefully with a
prototype implementation with measurements.
-- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net
Received on 2021-05-12 12:44:22