public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hewillk at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108362] New: views::istream is SFINAE-unfriendly
Date: Tue, 10 Jan 2023 15:24:06 +0000 [thread overview]
Message-ID: <bug-108362-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108362
Bug ID: 108362
Summary: views::istream is SFINAE-unfriendly
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: hewillk at gmail dot com
Target Milestone: ---
Similar issue with https://github.com/microsoft/STL/pull/3335.
#include <ranges>
#include <iostream>
template<class T>
concept can_istream_view = requires {
std::views::istream<T>(std::cin);
};
struct S { };
static_assert(!can_istream_view<S>);
https://godbolt.org/z/b3W1KsPWd
next reply other threads:[~2023-01-10 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 15:24 hewillk at gmail dot com [this message]
2023-01-13 0:19 ` [Bug libstdc++/108362] " redi at gcc dot gnu.org
2023-03-07 21:04 ` ppalka at gcc dot gnu.org
2023-03-09 18:35 ` cvs-commit at gcc dot gnu.org
2023-03-09 18:35 ` ppalka at gcc dot gnu.org
2023-04-29 14:04 ` cvs-commit at gcc dot gnu.org
2023-04-29 14:05 ` ppalka 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-108362-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).