https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #13 from Jonathan Wakely ---
Nice!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
Louis Dionne changed:
What|Removed |Added
CC||ldionne.2 at gmail dot com
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #11 from Jonathan Wakely ---
Author: redi
Date: Tue May 7 15:46:05 2019
New Revision: 270960
URL: https://gcc.gnu.org/viewcvs?rev=270960&root=gcc&view=rev
Log:
PR libstdc++/85965 delay static assertions until types are complete
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #10 from Jonathan Wakely ---
Author: redi
Date: Tue Mar 26 15:28:48 2019
New Revision: 269949
URL: https://gcc.gnu.org/viewcvs?rev=269949&root=gcc&view=rev
Log:
PR libstdc++/85965 delay static assertions until types are complete
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
Jonathan Wakely changed:
What|Removed |Added
Keywords||diagnostic
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #8 from Jonathan Wakely ---
Author: redi
Date: Tue Nov 21 20:47:09 2017
New Revision: 255035
URL: https://gcc.gnu.org/viewcvs?rev=255035&root=gcc&view=rev
Log:
PR libstdc++/48101 improve errors for invalid container specializations
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #7 from Jonathan Wakely ---
Even if we allowed allocator you still can't use std::set
because the container code assumes a non-const value type in several places.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #6 from Jonathan Wakely ---
You can't allocate const memory, but in essence yes, that's the reason. The
standard says that an allocator's value type must be a non-const, non-volatile
object type, so std::allocator is undefined behavio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #5 from gccbugs at jbapple dot com ---
What is the virtue of making std::allocator an error? Is this
required by the standard? Is it because calls to construct are writing to const
memory?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #4 from Jonathan Wakely ---
Which causes the code to be accepted. I'd rather do:
template class allocator; // undefined
so there's an error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
gccbugs at jbapple dot com changed:
What|Removed |Added
CC||gccbugs at jbapple dot com
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
Jonathan Wakely changed:
What|Removed |Added
CC||corey at octayn dot net
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48101
--- Comment #1 from Jonathan Wakely 2011-03-13
12:24:13 UTC ---
Do you have a suggestion for a better error? We could use a static_assert in
std::allocator to reject const T
As far as I can see, the reason the code is invalid is exactly the rea
14 matches
Mail list logo
