http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60965
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Andrew Haley from comment #8) > While it's true that we can play hardball on this one by insisting that only > char arrays should be used with placement new, it wouldn't really do any > good. I don't think it would make any real-world code more efficient. On the contrary, this bug is an example of making real code more efficient, just inappropriately because of the special status of char arrays. We really don't want to have to assume that any random object can invisibly change type, as that would make type-based optimizations pretty useless. As far as I know people always use char arrays for placement new anyway; at least all the examples I've ever seen do.
