deep_copy_ptr

[michael.li...@gmail.com]

The standard library already have reference counting and ownership transfering smart_ptr. But things become inconvenient when one wants to make a deep copy. I think standard should provide a smart_ptr direct support deep copy. Is there any standardization about deep_copy_ptr?

[Ville Voutilainen]

On 22 September 2013 17:57, <michael.li...@gmail.com> wrote:

The standard library already have reference counting and ownership transfering smart_ptr. But things become inconvenient when one wants to make a deep copy. I think standard should provide a smart_ptr direct support deep copy. Is there any standardization about deep_copy_ptr?

There's a proposal, http://open-std.org/JTC1/SC22/WG21/docs/papers/2012/n3339.pdf

[Klaim - Joël Lamotte]

On Sun, Sep 22, 2013 at 5:55 PM, Ville Voutilainen <ville.vo...@gmail.com> wrote:

There's a proposal, http://open-std.org/JTC1/SC22/WG21/docs/papers/2012/n3339.pdf

What was the reception of this proposal? What's it's current status?

[Ville Voutilainen]

It's still in the pipeline. There were some technical comments about it in Portland,
and I believe the author was encouraged to continue revising it.

[Klaim - Joël Lamotte]

On Tue, Sep 24, 2013 at 4:02 PM, Ville Voutilainen <ville.vo...@gmail.com> wrote:

It's still in the pipeline. There were some technical comments about it in Portland,
and I believe the author was encouraged to continue revising it.

Thanks.

[Philipp Stephani]

Has this proposal been discussed in the meantime?

[Ville Voutilainen]

On 8 July 2014 00:31, Philipp Stephani <p.ste...@gmail.com> wrote:
> Has this proposal been discussed in the meantime?

Not yet. It needs to be revised.

[Troy Heron]

Are there any notes on what specifically needs revising?

[David Krauss]

You might contact the author, Walter Brown. His email address has changed since then, though, so you should grab it from a newer proposal. He’s quite prolific.

[Ville Voutilainen]

On 30 July 2014 03:55, Troy Heron <troy....@hixxy.org> wrote:
> Are there any notes on what specifically needs revising?

The plan is to make it do type-erasure.

[Troy Heron]

Thanks Ville.

--

---
You received this message because you are subscribed to a topic in the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this topic, visit https://groups.google.com/a/isocpp.org/d/topic/std-proposals/oWfRXRHpVf4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to std-proposal...@isocpp.org.
To post to this group, send email to std-pr...@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.