https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110102
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Known to work| |14.0
Known to fail|14.0 |
Summary|[13/14 regression] |[13 regression]
|initializer_list ctors of |initializer_list ctors of
|containers skip |containers skip
|Allocator_traits::construct |Allocator_traits::construct
|, copies move-only type |, copies move-only type
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed on trunk so far.
(In reply to Arthur O'Dwyer from comment #6)
> Before C++20, I got tons of the same question for GCC's acceptance of
> int f(auto x) { return x; }
Looks like that was fixed in GCC 8.
> I still think it would be nice if GCC stopped supporting
> int f(std::vector<auto> v) { return v[0]; }
> , at least silently by default.
Fixed (to require -fconcepts-ts) on trunk.
