// 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 privat

// 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...