Incase it doesn’t show up:

  • Fushuan [he/him]
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    13 days ago

    I’ve not had those while working with concurrent programs with c++ for over a year. Pointers, QT programming, non-qt backend programming, coding an engine to work with computer vision runners (openvino mostly), image management (more pointers)… Idk, this is gonna sound rude but just code better? Most of my errors were segfaults, I have had to plug the debugger and/or tons of prints and I made it work.

    If you want to see giant error logs, check pyspark errors. But even those have the relevant line of info and then all the rest of the garbage info that no one really needs, like any other language.

    • xthexder@l.sw0.com
      link
      fedilink
      arrow-up
      3
      ·
      13 days ago

      It really depends what you’re doing. The last big project I did with C++ templates was using them to make a lot of compile-time guarantees about concurrency locks so they don’t need to be checked at runtime (thus trading my development time for faster performance). I was able to hide the majority of the templates from users of the library, and spent extra time writing custom static_assert messages.

      C++ templates are in fact a compile-time turing complete language, as crazy as that sounds.