https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112349
--- Comment #6 from Ted Lyngmo ---
I think this can be closed. I think this was fixed in 14.2.1 if I'm not
mistaken.
NCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
The following results in `error: parameter packs not expanded with '...'` in
all versions of g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116714
--- Comment #6 from Ted Lyngmo ---
Darn... :-) Glad you're on it!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116714
--- Comment #4 from Ted Lyngmo ---
Andrew: The reduced example you provided is not interpreted the same way as
what I used when I wrote the report. I think they fail for different reasons.
Possibly at different stages. I went through the languag
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
The lambda type `type` is here used to instantiate two objects, i1 and i2. They
are clearly of the same type since `std
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107087
Ted Lyngmo changed:
What|Removed |Added
CC||ted at lyncon dot se
--- Comment #20 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116051
--- Comment #1 from Ted Lyngmo ---
I realized that T in the working usages is non-dependent. I think we can close
this right away.
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
I believe this is related to
https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#577
```
#include
template
struct Foo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114625
--- Comment #5 from Ted Lyngmo ---
@Andrew, the title change seems wrong. It wrongly returns true when T{} is
ill-formed.
|accepted when T{} is|accepted when T{} is
|ill-formed |ill-formed while in concept
CC||ted at lyncon dot se
--- Comment #1 from Ted Lyngmo ---
The assertion correctly fails with this though
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
This program compiles but I'd expect both `static_assert`s to refuse it since
`d x{};` is invalid.
```
#include
template
co
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
gcc accepts `NonStructuralType` as a non-type template parameter type below:
```
struct StructuralType1 {
constexpr StructuralType1(int A
++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
From:
https://stackoverflow.com/questions/77409266/why-does-gcc-copy-object-for-each-comparison-in-stdrangesmax
OP's sample program shows a copy being made for each compa
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.
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"?
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
Compiling this in C++20 mode on trunk (https://godbolt.org/z/dW5cf3WrK):
```
template
struct foo {
template
void bar() {}
};
int main
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
This works up to 12.2 (inclusive) on godbolt but fails on trunk:
```
template
struct base {
friend void foo(const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106110
--- Comment #1 from Ted Lyngmo ---
Sorry, the helper variable template should be:
```
template
static constexpr bool is_foo_call_ambiguous_v =
is_foo_call_ambiguous::value;
```
It gives the same result: https://godbolt.org/z/bKbn8Gre7
++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
I made a type trait to test if a call to a function using certain arguments
would be ambiguous or not, but in the below example, where I expected that
calling the function `foo` with a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105637
--- Comment #5 from Ted Lyngmo ---
Excellent and thanks!
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
This compiles fine in 11.3 but selects the non-const `BaseClass` overload in
12.1:
```
struct BaseClass {
// Commenting out this non-const function out will fix the
++
Assignee: unassigned at gcc dot gnu.org
Reporter: ted at lyncon dot se
Target Milestone: ---
Regression between g++ 9.4 and 10.1:
```
struct apa {
constexpr auto n() const { return 3; }
};
template
constexpr auto f() {
apa foo;
int{foo.n()}; // no matching function for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86581
Ted Lyngmo changed:
What|Removed |Added
CC||ted at lyncon dot se
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81486
Ted Lyngmo changed:
What|Removed |Added
CC||ted at lyncon dot se
--- Comment #3 from
24 matches
Mail list logo
