https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102482
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jonathan Wakely from comment #5) > True, but approximately nobody writes constructors taking a non-const lvalue > reference to std::initializer_list, so this corner case doesn't seem very > important. This does seem like a concrete enhancement that could be made > easily though, even if low value in practice. Just to make this bit easier to find in my wall of text above: The warning should not trigger if the constructor takes the initializer_list by non-const lvalue reference.
