>
> Great link, it looks as though many of our Try<T> / Option<T> / Result<T> /
> Future<T> functions that return different results based on parameters /
> runtime conditions (e.g. t, None(), Error("..."), Failure("...")) will not
> have copies elided via NRVO? (these look similar to cases N and O in the
> doc).


Ben, your observation there is accurate. It's a case we either call it
"good enough" or consider it as a special case to remember to explicitly
move them out.

In relation to this particular proposal, these don't kick in even if we try
capturing it by *const-ref*.

Tested with gcc-4.7.4 and gcc-4.8.4.

MPark.

Reply via email to