• @lysdexic@programming.devM
    link
    fedilink
    English
    -62 months ago

    The problem with C++ is it still allows a lot of unsafe ways of working with memory that previous projects used and people still use now.

    Why do you think this is a problem? We have a tool that gives everyone the freedom to manage resources the way it suits their own needs. It even went as far as explicitly supporting garbage collectors right up to C++23. Some frameworks adopted and enforced their own memory management systems, such as Qt.

    Tell me, exactly why do you think this is a problem?

      • @FizzyOrange@programming.dev
        link
        fedilink
        72 months ago

        It’s not just that. Debugging segfaults and UB can be an absolute nightmare.

        The C++ committee still haven’t learnt their lesson. I recently learnt about C++20 coroutines, which are pretty neat, if complex (there are pretty much no good learning resources about them). However they are still putting unnecessary UB footguns in it.

        • lad
          link
          fedilink
          English
          42 months ago

          Reminds me of how I found some safety measures to be in China some years back, basically those were signs saying “plz don’t fall to your death, if you do it’s your fault”

          • @lambalicious
            link
            English
            12 months ago

            At least it’s not like Russia, where it’s “plz don’t fall to your death, if you do it’s our fault”…

            • lad
              link
              fedilink
              English
              22 months ago

              I thought a lot of places are like that, that’s why we get all the fences and such 🤔

        • bufalo1973
          link
          fedilink
          118 days ago

          Maybe a “pragma strict” where every deprecated is an error and not a warning?