We like it too, which is why we are planning on having a second template parameter for persistent, a traits class, which will control whether a handle is copyable, etc. We're undecided on what the default template parameter will be, but at first it will have to implement the current semantics to keep things sane.
On Monday, August 5, 2013 11:38:38 AM UTC+2, Ben Noordhuis wrote: > > On Mon, Aug 5, 2013 at 9:01 AM, Dan Carney <[email protected]<javascript:>> > wrote: > >> Good. > >> Will we be able to copy persistent? In my case I have to be able to > pass > >> around a persistent and store it in several places at a time. > >> Or should I wrap it in another object and ref count it myself? > > > > > > It will be copyable, but copying will become more expensive, as the > backing > > store needs to be copied. > > As a counterpoint, I like that Persistent<T> is non-copyable now. It > makes it much easier to reason about its life cycle and ownership. I > would move to keep it like this. > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
