https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105595
--- Comment #9 from dennis-hezel at gmx dot de ---
Yes it is also true for functions in anon namespace inside header. Again, I am
not so concerned with getting all of those scenarios perfectly fixed. Like you
were saying, it probably requires som
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105595
--- Comment #7 from dennis-hezel at gmx dot de ---
I am perfectly happy with a fix just for coroutines!
I do not have any code that contains your reproducer. It would also be a code
smell: struct Y defined inside cpp file but not in anon namespa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105595
--- Comment #5 from dennis-hezel at gmx dot de ---
> naturally, if you never include this file twice, it should be okay
That is exactly the point. Whenever a file with your `namespace { struct X {};
}` example or the coroutine example is include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107556
Bug ID: 107556
Summary: Passing lambda to a coroutine function triggers
-Wsubobject-linkage
Product: gcc
Version: 10.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485
Bug ID: 101485
Summary: Calling std::equal with std::byte* does not use memcmp
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
