Live data from Hacker News

Viewing profile — pkasting

pkasting

HN member
Joined
Tue, Jul 03, 2012, 6:09 AM UTC
HN karma
758
Public activity
95 items

About pkasting

[ my public key: https://keybase.io/pkasting; my proof: https://keybase.io/pkasting/sigs/sLo64RRHO3BEoz4IwHQ4Siph2FI6BHWTY0bZHFAGktY ]

Recent public activity

  1. comment
    Comment #49171418

    Ray Bradbury is the best horror writer to have worked in a sci-fi milieu. This story is one of only a couple sci-fi short stories to creep me out enough that I still remember them …

  2. comment
    Comment #49114903

    The closing problem is more fun. > A man is twice the age his wife was when he was the age she is now. When she reaches his present age, their combined years will be 100. Find the …

  3. comment
    Comment #48981588

    I was there 06-25, and this matches my recollection. Honestly, it's a very restrained document.

  4. comment
    Comment #48572878

    The idea sounds good, even if Epic's recent track record of tools is not inspiring. But the commit messages etc. are very clearly products of vibe-coding. And version control is no…

  5. comment
    Comment #48079643

    XHTML was never all the rage. Your premise is false. Hard errors up front are great when you control the full content pipeline. It's very rare that that's the case, and was rare ev…

  6. comment
    Comment #48079625

    On the contrary, image decoders all run complex processes that try and guess what to do in erroneous cases. I used to maintain Chrome's image decoders, and every single image forma…

  7. comment
    Comment #47853656

    (Tangent: What a pleasure to see your username again; will always think of your readability help fondly!)

  8. comment
    Comment #47850581

    This list is missing my personal law, Kasting's Law: Asking "who wrote this stupid code?" will retroactively travel back in time and cause it to have been you.

  9. comment
    Comment #47570456

    Crowing over omitting Arabic numerals in the name of avoiding any kind of cultural influence or bias seems silly when everything is still going to be expressed in decimal.

  10. comment
    Comment #46746862

    C++ module implementation is a story with a lot of drama, if you ever want to read up on it. The short summary, though, is that no toolchain yet has a bulletproof implementation, t…

  11. comment
    Comment #46746838

    Yeah, maintainers would certainly +1 a CL that added a note about the parts of //base to use instead. Trivial oversight.

  12. comment
    Comment #46746662

    FWIW, I still think the Google Style Guide banning UDLs entirely is too harsh. I think they should be used sparingly, but there are cases where they make sense. In Chromium's UI co…

  13. comment
    Comment #46746626

    A cursory Chromium code search does not find anything outside third_party/ forcing either signed or unsigned char. I suspect if I dug into the archives, I'd find a discussion on cx…

  14. comment
    Comment #46746590

    Dunno! My last project there was to add support for one of the TI DSPs, but as I said, that's decades past now. Anyway, I think there are two takeaways: 1. There probably do exist …

  15. comment
    Comment #46746550

    Yes, reading the actual data would still be UB. Hopefully will be fixed in C++29: https://github.com/cplusplus/papers/issues/592

  16. comment
    Comment #46746513

    At least in Chromium that wouldn't help us, because we disable strict aliasing (and have to, as there are at least a few core places where we violate it and porting to an alternati…

  17. comment
    Comment #46746473

    When I led C++ style/modernization for Chromium, I made this argument frequently: we should prefer the stdlib version of something unless we have reason not to, because incoming en…

  18. comment
    Comment #46744623

    It's weird to me, as the former lead maintainer of this page for ten years or so, that this got submitted to both r/c++ and HN on the same day. Like... what's so exciting about it?…

  19. comment
    Comment #46744598

    The majority of things Chromium bans would still get banned in green-field use. Some notable exceptions: we'd have allowed std::shared_ptr and . We might also have allowed and frie…

  20. comment
    Comment #46744565

    This bit us in Chromium. We at least discussed forcing the compiler to use unsigned char on all platforms; I don't recall if that actually happened.

  21. comment
    Comment #46744546

    Green Hills Software's compiler supports more recent versions of C++ (it uses the EDG frontend) and targets some DSPs. Back when I worked in the embedded space, chips like ZSP were…

  22. comment
    Comment #46744528

    I don't think that's an accurate representation. There are a few features like that, but the majority of things banned in the Google style guide are banned for safety, clarity, or …

  23. comment
    Comment #46744469

    Both parts of your sentence refer to the Google style guide. This doc isn't the Google style guide. It's the Chromium modern c++ features doc. We don't talk about exceptions or pla…

  24. comment
    Comment #46744446

    We have base::Callback for when you'd reach for std::function, which provides superior safety.

  25. comment
    Comment #46744419

    Sure; you can roll your own, or you can use one of the many other libraries that provide alternatives. There are obvious downsides to the former, and the latter is basically equiva…