Subject: Re: [boost] [ Interest? ] [ out_ptr ] Tiny C++ Abstraction for C-Style Output Pointers
From: JeanHeyd Meneide (phdofthehouse_at_[hidden])
Date: 2019-05-11 21:03:03
Dear Boost Community,
I have been working with both Boost and Standards Committee members
for the past 6 montha to deliver an implementation of out_ptr, inout_ptr,
and associated customization points to both the standard and Boost.
Currently, there is a (new) public implementation using only Boost
and consumable from C++11 compilers: https://github.com/ThePhD/out_ptr .
As a recap of what has happened:
- An attempt was made to put an implementation of this into Boost.Move,
partly to ensure a friend-implementation of the customization point for
boost::movelib::unique_ptr could be done for performance reasons. It was
suggested to try Boost.SmartPtr instead.
- A discussion of implementation, specification, performance and
suitability was undertaken by myself, Mr. Peter Dimov and Mr. Glen
Fernandes for Boost.SmartPtr while the proposal was moved through the
standard: https://github.com/boostorg/smart_ptr/issues/56 . An
implementation was made with different design choices and that experience
was passed on to me, which I incorporated into the current C++11 design.
- I privately created and used an implementation and shared it with others
and their codebases, gaining feedback.
- For C++Now Library in a w
Week, I focused on creating a version of Boost.out_ptr suitable for
inclusion into Boost. There was an initial in-person review. The result of
that review is documented in the rationale:
- There is now a public boost-ready (I feel) implementation.
In a week or two, I feel like -- given the amount of input on the
design and specification by seversl boost and non-boost members, shows of
curiosity and support in person, twitter, and on Slack, and feedback about
documentation from several users -- I should prepare to move into a Review
Queue by getting such a motion seconded.
Do let me know if the level of interest for this library in Boost is
still present and if taking the next steps is justified! It would be nice
to have a C++11 implementation in Boost even after this finishes landing