From: Stefan Ring <stefanrin@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Guaranteed copy elision
Date: Fri, 18 Nov 2022 16:05:33 +0100 [thread overview]
Message-ID: <CAAxjCEybwpBm05QtUEHPpfzfJ39mvqiXWRGAC164Ggw=X9o41w@mail.gmail.com> (raw)
In-Reply-To: <CAJYFCiO-gkmFEw+pyPigb-NC6bYaqjLU2Eb9ZoQE2mOSNw9fNA@mail.gmail.com>
On Tue, Nov 15, 2022 at 6:48 AM Yubin Ruan via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> To be sure that a object would not be copied, we usually write something
> like
>
> SomeBigObject obj;
> func(&obj);
>
> while in most of the cases a one-liner like
>
> SomeBigObject obj = func();
>
> would suffice.
>
> Is there any language facility to help us guarantee that at compile time
> (such as some kind of static_assert() ) so that we can be confident writing
> those one-liner ?
Interesting question, but unfortunately I do not have a good answer! I
can only bump the thread. ;)
next prev parent reply other threads:[~2022-11-18 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 5:47 Yubin Ruan
2022-11-18 15:05 ` Stefan Ring [this message]
2022-11-18 21:35 ` Martin Oberzalek
2022-11-18 21:58 ` Segher Boessenkool
2022-11-19 10:07 ` Jonathan Wakely
2022-11-19 10:12 ` Jonathan Wakely
2022-11-21 14:17 ` Yubin Ruan
2022-11-21 14:20 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAxjCEybwpBm05QtUEHPpfzfJ39mvqiXWRGAC164Ggw=X9o41w@mail.gmail.com' \
--to=stefanrin@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).