https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86186
--- Comment #4 from Jonathan Wakely ---
If you want to suggest that GCC should have a new warning, then say that.
Don't past valid code and incorrectly claim that clang rejects it, or provide a
link to a bug in libc++ which is completely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86186
--- Comment #3 from Jonathan Wakely ---
(In reply to zhonghao from comment #2)
> (In reply to Jonathan Wakely from comment #1)
> > (In reply to zhonghao from comment #0)
> > > A previous version of clang++ does not produce any error messages for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86186
--- Comment #2 from zhonghao at pku dot org.cn ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to zhonghao from comment #0)
> > A previous version of clang++ does not produce any error messages for the
> > above code, but it was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86186
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
