[Bug libstdc++/119899] Custom invoke has name collision with std::invoke, without using namespace std

2025-04-23 Thread frederik.hofe at pm dot me via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119899 --- Comment #6 from Frederik vom Hofe --- Thx, good it! Basically template libraries might want to make heavy use of function-name-brackets, e.g. (invoke), to prevent the lookup using pulled in namespaces from parameter types.

[Bug libgcc/119899] New: Custom invoke has name collision with std::invoke, without using namespace std

2025-04-22 Thread frederik.hofe at pm dot me via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119899 Bug ID: 119899 Summary: Custom invoke has name collision with std::invoke, without using namespace std Product: gcc Version: 16.0 Status: UNCONFIRMED Severity:

[Bug c++/119548] New: ICE: tree check: accessed elt 2 of 'tree_vec' with 1 elts in tsubst_pack_expansion when accessing uninstantiated decltype(lambda template return) type, inside other lambda templ

2025-03-31 Thread frederik.hofe at pm dot me via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119548 Bug ID: 119548 Summary: ICE: tree check: accessed elt 2 of 'tree_vec' with 1 elts in tsubst_pack_expansion when accessing uninstantiated decltype(lambda template return) type,