[Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context

2023-07-11 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595

--- Comment #8 from Ted Lyngmo  ---
:-) Ok I tried understanding the Status by reading
https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html#bug_status but it doesn't
mention NEW. But ok, as long as it's actually a confirmed bug, I'm good.

[Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context

2023-07-11 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595

--- Comment #7 from Andrew Pinski  ---
(In reply to Ted Lyngmo from comment #6)
> @Andrew Pinski: Shouldn't the status be "CONFIRMED" rather than "NEW"?

There is status called confirmed but rather rhe new status is the confirmed
state.

[Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context

2023-07-11 Thread ted at lyncon dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595

--- Comment #6 from Ted Lyngmo  ---
@Andrew Pinski: Shouldn't the status be "CONFIRMED" rather than "NEW"?

[Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context

2023-07-11 Thread ppalka at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595

Patrick Palka  changed:

   What|Removed |Added

 CC||ted at lyncon dot se

--- Comment #5 from Patrick Palka  ---
*** Bug 110604 has been marked as a duplicate of this bug. ***

[Bug c++/93595] [c++20] function call, substitution failure of template paramter with a lambda default in template context

2021-12-19 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595

Andrew Pinski  changed:

   What|Removed |Added

 CC||barry.revzin at gmail dot com

--- Comment #4 from Andrew Pinski  ---
*** Bug 102644 has been marked as a duplicate of this bug. ***