https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70511
--- Comment #2 from Ivan Le Lann ---
It seems that this has been "fixed".
Fedora 24, using "gcc (GCC) 6.1.1 20160510 (Red Hat 6.1.1-2)" gives me the
intuitive behavior.
I did a local revert of this this commit
https://github.com/gcc-mirror/gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70511
--- Comment #1 from Ivan Le Lann ---
After a quick look, I'm not sure this can be called a bug.
It looks like a very unfortunate consequence of library specification.
From the mess here
http://en.cppreference.com/w/cpp/utility/tuple/tuple
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: ivan.lelann at free dot fr
Target Milestone: ---
This code compiles fine :
#include
#include
#include
int main()
{
boost::any val = 12.0;
std::tuple tuple_test {val};
std::cout << std:
