https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107784
--- Comment #6 from Jörg Richter <joerg.rich...@pdv-fs.de> ---
It's not that I'm intentionally using bind_front without further arguments. I
just stumbled across it when I was developing code that could output the target
of a std::function<>. As I've stumpelt upon it, I might as well report it
instead of ignoring it.
In the process, I also noticed that bind_front( one, two, three ) is stored in
memory as { one, three, two }. Here it would also help me a lot if the order is
kept. But I think that would be too big of an ABI change. Too bad. But if this
is considered, I could also create another QoI PR.
Regardless, I've come across a few posts that find the recursive implementation
of std::tuple out of date.
It would be nice if libstdc++ had a mode to enable such incompatible
enhancements, since we compile all our C++ code ourselves and thus
automatically never have ABI issues.
