The std::weak_ptr does need a shared_ptr, but that doesn't necessarily
prevent them from creating their own 'weak_reference' class or whatever
that could check on whether what it pointed to was still valid or not.
The case I'm using it for is I have a top level message, with a repeated
set of s
There is no fixed time for release. Usually it's around a quarter.
On Mon, Jul 24, 2017 at 9:21 AM Arpit Baldeva wrote:
> Thanks.
>
> In general, is there a release schedule? Like once a quarter, once every X
> weeks etc?
>
>
>
> On Friday, July 21, 2017 at 2:46:34 PM UTC-7, Bo Yang wrote:
>
>>
A weak_ptr needs a shared_ptr to begin with so all the submessages would
end up being a shared_ptr (creating an impression that they are meant for
shared ownership). In fact, I feel that Protobuf could perhaps change the
generated code to use unique_ptr instead of it's raw pointers to more
clea
Thanks.
In general, is there a release schedule? Like once a quarter, once every X
weeks etc?
On Friday, July 21, 2017 at 2:46:34 PM UTC-7, Bo Yang wrote:
>
> https://github.com/google/protobuf/milestone/20
> ETA is end of this month.
>
> On Thu, Jul 20, 2017 at 1:26 PM Arpit Baldeva > wrote:
