• @[email protected]
    link
    fedilink
    03 months ago

    This is cool in theory but this is yet another competing standard of static analysis.

    We got clang-tidy, CPPAnalyser, etc… etc…

    • @[email protected]
      link
      fedilink
      03 months ago

      I am also curious how much of those “%80 of the bugs” would be detected by tools like valgrind, CPPcheck etc. If a major part, then the main problem is people not incentivized to / not having enough time to use these tools.

    • moxOP
      link
      fedilink
      0
      edit-2
      3 months ago

      this is yet another competing standard of static analysis.

      No, it isn’t.

      Those are linters. They might or might not discover problematic use of unsafe language features lurking in existing code.

      This proposal is a new iteration of the language and standard library. It would provide safe language features for preventing such problems existing in the first place.

      • @[email protected]
        link
        fedilink
        0
        edit-2
        3 months ago

        Right now, we have to compile the compiler for this ourselves. Pardon my skepticism; I’m not sure this is mature enough.

        Edit: I’m talking about the project not the idea. Sean Baxter has shown up everywhere for awhile talking about this. I think his idea has a ton of maturity. I don’t know that the project itself has enough maturity to mainline yet.

        • moxOP
          link
          fedilink
          03 months ago

          That’s fair. I think the last word in the URL does a good job of representing the implementation’s claimed level of maturity:

          draft

          :)

          • @[email protected]
            link
            fedilink
            03 months ago

            You said

            This proposal is a new iteration of the language and standard library. It would provide safe language features for preventing such problems existing in the first place.

            Either it’s a draft or it’s a new iteration of the language. Can’t be both.

            • moxOP
              link
              fedilink
              03 months ago

              Either it’s a draft or it’s a new iteration of the language. Can’t be both.

              It’s a draft of a proposal for a new iteration. Is that so difficult for you to understand?

                • @[email protected]
                  link
                  fedilink
                  03 months ago

                  He never said it was an Internet Draft. Try actually reading. It might help you in the future when you are discussing things.

                • moxOP
                  link
                  fedilink
                  03 months ago

                  https://en.wikipedia.org/wiki/Internet_Draft

                  I think it’s pretty clear that IETF drafts are not what author meant when he wrote draft, and I’m pretty sure the IETF doesn’t have much to do with C++ standards.

                  Are you under the impression that there is no other sense of the word?

                  It might help you in the future when you are discussing things like drafts, specifications, and proposals.

                  As it turns out, I have done more than a little of that. Thankfully, I don’t usually see such condescending remarks in the process, nor such insistence on misunderstanding. Good luck to you, too.