// In case it's not clear: I am not suggesting you *actually* do this!
A more practical but still dubious takeaway would be that you can safely `#define private public` and `#define protected public` to work around the visibility and you still get a syntactically correct C++ code. Of course, you are doomed if ABIs start to depend on the visibility...
// This started as a tweet with a joke of "C++ pro-tip: #define private public",
// and then it quickly escalated into more and more evil suggestions.
// I've tried to capture interesting suggestions here.
// In case it's not clear: I am not suggesting you *actually* do this!
Obviously, C and C++ have characteristics driving people to desperately try Twitter pro-tips. To stuff something like this under the door, I believe your PR better mention Jenkins.
Too obvious and easy to clean up. Depending on how things were when you left, a passive aggressive commit message with whatever work you had left uncommitted is easiest.
It isn't mysterious. It just doesn't match the vibes of HN. I don't come on HN to see silly jokes. And as you can see by the number of flags this post has received to kill it, it looks like most HN readers agree with me.
