gotta admit the context here (Linux kernel) makes one wonder if they should be doing this
http://www.openwall.com/lists/kernel-hardening/2018/04/15/1 …
(via @mfukar)pic.twitter.com/BcoGCteN9D
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
as in, context is a union of (struct camellia_ctx, ...)? Probably the most reasonable.
I don't think this it what Rich was referring to. This thread is about poor man's subtyping, not poor man's polymorphism. Keep using unions for poor man's polymorphism, it's the usecase that doesn't have problem (using them for type-punning has problems, but no type-punning here)
I believe that Rich was saying was that for poor man's subtyping, you should write: struct colored_dot { struct dot d; int color; }; instead of: struct colored_dot { int x; int y; int color; };
Yes. Then you can safely deref struct colored_dot * as struct dot *, by initial member rule.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.