Before anyone flips out, he actually merged the code: https://lkml.org/lkml/2018/6/5/774

    Side note: I've merged it, and it's going through my build tests, 
    so it's really not that I hate the code.

    But I really find that kind of one-sided rationale that ignores reality unacceptable.

    And I find it dangerous, because it *sounds* so "obviously correct" to people who don't know any better. 
    If you don't know that gcc explicitly says that you should use unions to do type punning to avoid aliasing issues, 
    you might believe that union type punning is a bad thing from that commit message.

    So it's dangerously misleading, because lots of people have a dangerous reverence for paper over reality.

    In programming, "Appeal to Standards" should be considered a potential logical fallacy. 
    Standards have their place, but they definitely have their caveats too.