Displaying 2 results from an estimated 2 matches for "unique_ref".
Did you mean:
unique_len
2013 Nov 22
0
[LLVMdev] ErrorOr<> conflicts with unique_ptr<>
...dereferences.
But yes, broadly it is kind of annoying - personally I have fantasy ideas
of overloading operator '.', having a unique_ptr that was never-null and
thus didn't model a pointer (and overloaded operator '.' for access to the
underlying object) and then composing this unique_ref with ErrorOr would
just add one level of pointery-ness, not two.
- Dave
>
> -Nick
>
>
>
>
>> }
>>
>> void sinkEU(ErrorOr<std::unique_ptr<Foo>> f) {
>> f->doit(); // ERROR: no member named 'doit' in
>> 'std::__1::unique_...
2013 Nov 22
3
[LLVMdev] ErrorOr<> conflicts with unique_ptr<>
On Nov 21, 2013, at 4:07 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
>
>
> On Thu, Nov 21, 2013 at 3:57 PM, Nick Kledzik <kledzik at apple.com> wrote:
> Michael,
>
> In lld, we have places that used nested a ErrorOr<std::unique_ptr<xx>> and I often hit compiler errors that require breaking up expressions to work around. Do you have