I probably should have done something besides read these comments https://www.reddit.com/r/programming/comments/62091n/its_time_for_a_memory_safety_intervention/ …pic.twitter.com/AO88Q0jJWz
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
No, don't say that. Everyone will think they're in that bucket!
Everyone should be realizing if they're not in that bucket they need to throw out and replace their crap code.
A much bigger problem than C is the attitude that writing C is a license to write whatever crap you want and call it C
...then whine that C is "supposed to be" "high level assembler" and you should be able to do whatever you like.
No. This isn't about strict aliasing violations. This is about (unexpected) aliasing issues *in general*
My point is that there are no "unexpected" aliasing issues unless you type pun.
every time somebody accidentally passes overlapping/identical pointers to memcpy is an unexpected aliasing issue
OK, we're using words differently then. I just call that a violation of interface contract for memcpy.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.