From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-rust@gcc.gnu.org
Subject: [Bug rust/108111] Rust meets clang
Date: Wed, 14 Dec 2022 22:22:20 +0000 [thread overview]
Message-ID: <bug-108111-35322-fLMkZj9vdk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108111-35322@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108111
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Marc Poulhiès from comment #1)
> I'll need to read a bit more about the 8 (default move assignment op being
> deleted).
Lexer has this member:
buffered_queue<int, InputSource &> input_queue;
That has a member of type InputSource& which means it is not assignable, so
Lexer is not assignable either.
Are you sure you want a reference there?
Using std::reference_wrapper<InputSource> would work without needing to change
buffered_queue.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-14 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 19:17 [Bug rust/108111] New: " dcb314 at hotmail dot com
2022-12-14 21:46 ` [Bug rust/108111] " dkm at gcc dot gnu.org
2022-12-14 22:22 ` redi at gcc dot gnu.org [this message]
2022-12-15 10:44 ` marxin at gcc dot gnu.org
2022-12-15 11:49 ` redi at gcc dot gnu.org
2022-12-15 20:22 ` dkm at gcc dot gnu.org
2023-03-10 3:17 ` dkm at gcc dot gnu.org
2024-01-16 17:24 ` cvs-commit at gcc dot gnu.org
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=bug-108111-35322-fLMkZj9vdk@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-rust@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).