Displaying 2 results from an estimated 2 matches for "erroor".
Did you mean:
error
2013 Nov 22
0
[LLVMdev] ErrorOr<> conflicts with unique_ptr<>
...T* 't', then I would expect to write "t->bar()" (or
"(*t).bar()") to call bar.
If I have an ErrorOr<T> 'e', then ErrorOr provides operator* and operator->
to access the underlying T. So I would write "e->bar()" or "(*e).bar()".
ErroOr acts as though it's a pointer to T.
If I had a T** 't', then I would expect to write "(*t)->bar()" or
"(**t).bar()".
So by analogy, if I have an ErrorOr<T*> I would expect to write
"(*e)->bar()" or "(**e).bar()".
Now replace T* with...
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