this post was submitted on 13 Sep 2024
53 points (94.9% liked)
Programming
17024 readers
255 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is cool in theory but this is yet another competing standard of static analysis.
We got clang-tidy, CPPAnalyser, etc… etc…
I am also curious how much of those "%70 of the vulnerabilities" would be detected by tools like valgrind, CPPcheck etc (either directly in the former case or indirectly in the latter). If a major part, then the main problem is people not incentivized to / not having enough time to use these tools.
Valgrind is pretty crazy to find bugs and memory leaks !
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.
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.
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
:)
You said
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 to understand?
Annnnnnnnnnnnd we’re done. Good luck! I highly recommend you take some time to understand how draft can mean more in the technical space. It might help you in the future when you are discussing things like drafts, specifications, and proposals.
He never said it was an Internet Draft. Try actually reading. It might help you in the future when you are discussing things.
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?
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.
This is “It’s just a THEORY” but for programmers
It’s a concept of a plan