https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115908
--- Comment #9 from Artyom Kolpakov ---
Has this bug been fixed?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117410
--- Comment #5 from Artyom Kolpakov ---
Here is a slightly different example:
template
void foo(int = 0) {}
template
void foo(...) requires true {}
int main() {
foo();
}
The current standard contains ambiguity regarding ellipsis. I sug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117410
--- Comment #3 from Artyom Kolpakov ---
(In reply to Jonathan Wakely from comment #2)
> But without the variadic arguments, the functions have equivalent function
> parameter lists, so the constraints are checked. With the ellipsis, they do
> no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117410
Bug ID: 117410
Summary: Ambiguous overload with ellipsis
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117374
Bug ID: 117374
Summary: Strange behavior of co_yield in initializer-list
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117269
Bug ID: 117269
Summary: Lambda with capture is accepted as NTTP
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80943
Artyom Kolpakov changed:
What|Removed |Added
CC||ddvamp007 at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115905
--- Comment #2 from Artyom Kolpakov ---
I apologize very much. Not having figured out who the actual developer of clang
is, I took third persons opinions as the organization's opinion and used that
to create the further discussion. As it was poi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115905
Artyom Kolpakov changed:
What|Removed |Added
See Also||https://github.com/cplusplu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115908
--- Comment #7 from Artyom Kolpakov ---
(In reply to Iain Sandoe from comment #6)
> fixed on trunk, waiting for possible back-port
I'm not sure if I should write this here, but now a warning has appeared in the
original example: unused paramete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115908
--- Comment #2 from Artyom Kolpakov ---
When I wrote about returning the reference, i meant the return type of
get_return_object(), and not the coroutine itself
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115908
Bug ID: 115908
Summary: [coroutines] Wrong behavior of using
get_return_object() coroutines creation
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115906
Bug ID: 115906
Summary: [coroutines] ICE when co_await used as default
argument in function declaration
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115905
Bug ID: 115905
Summary: [coroutines] Wrong behavior of await_suspend()
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
14 matches
Mail list logo
