Displaying 4 results from an estimated 4 matches for "ny95nh".
2020 Oct 01
2
[EXTERNAL] Re: preferred way to return expected values
On Thu, Oct 1, 2020 at 2:08 AM George Rimar <grimar at accesssoftek.com> wrote:
> FWIW, I've performed an experiment with the code below at godbolt.
> (used -O2, https://godbolt.org/z/nY95nh)
>
> ```
> #include <vector>
> #include "llvm/Support/Error.h"
>
> llvm::Expected<std::vector<int>> foo() {
> std::vector<int> V;
> V.push_back(0);
> return V;
> }
> ```
>
I think the easiest and portable way to test this fun...
2020 Sep 28
2
preferred way to return expected values
Many thanks for the reply,
right, this is what the discussion is about.
On Mon, Sep 28, 2020 at 10:57 AM David Blaikie <dblaikie at gmail.com> wrote:
> To clarify, this is a discussion around whether given some move-only type
> X, implicitly convertible to Y and the code "Y func() { X x; return x; }"
> is that valid in LLVM? (and, as a corollary, if the type isn't
2020 Oct 02
2
[EXTERNAL] Re: preferred way to return expected values
...] Re: [llvm-dev] preferred way to return expected
> values
>
>
>
> On Thu, Oct 1, 2020 at 2:08 AM George Rimar <grimar at accesssoftek.com>
> wrote:
>
>> FWIW, I've performed an experiment with the code below at godbolt.
>> (used -O2, https://godbolt.org/z/nY95nh)
>>
>> ```
>> #include <vector>
>> #include "llvm/Support/Error.h"
>>
>> llvm::Expected<std::vector<int>> foo() {
>> std::vector<int> V;
>> V.push_back(0);
>> return V;
>> }
>> ```
>>
>
&...
2020 Oct 02
2
[EXTERNAL] Re: preferred way to return expected values
...turn expected
>> values
>>
>>
>>
>> On Thu, Oct 1, 2020 at 2:08 AM George Rimar <grimar at accesssoftek.com>
>> wrote:
>>
>>> FWIW, I've performed an experiment with the code below at godbolt.
>>> (used -O2, https://godbolt.org/z/nY95nh)
>>>
>>> ```
>>> #include <vector>
>>> #include "llvm/Support/Error.h"
>>>
>>> llvm::Expected<std::vector<int>> foo() {
>>> std::vector<int> V;
>>> V.push_back(0);
>>> return V;
>...