https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92224
--- Comment #4 from Jonathan Wakely ---
It's undefined, so the implementation is not required to give an error. To
quote the standard:
Undefined behavior may be expected when this document omits any explicit
definition of behavior or when a prog
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92224
--- Comment #3 from Mario Galindo ---
Thank you sir. As clang is allowing this type of construction, I believe now
that the "bug" is in clang, not gcc. Regards.
Dr. Ing. Mario Galindo Q.
Cel: 591-72062746 & 591-72010422
On 25 Oct 2019 06:20, "r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92224
--- Comment #2 from Jonathan Wakely ---
Also, set keys are *not* const, otherwise you wouldn't be able to assign one
set to another set without reallocating every element.
std::set::iterator only gives you const *access* to the elements, but the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92224
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
