🚀 go-pugleaf

Request for Clarification and a General Proposal:

I claim there is a need for clarification in terms of what kinds of ptr
casts are legal in the face of an optimizing compiler.  For example, does:

	foo* fooptr = &(bar.fooMember);

poison fooMember, the labeled section fooMember is in, the class derivation
that fooMember is in, or all of bar?

My general proposal is that C++ be very restrictive in terms of what pointer
casts are "guaranteed" to work, allowing for maximum compiler optimizations,
while minimizing the pointer hacks that are "guaranteed" to work.  IE,
good C++ citizens should get well optimized code, but C++ hacker code may
not work at all.