On 2/25/26 00:35, Jason McKesson via Std-Discussion wrote:
On Tue, Feb 24, 2026 at 8:33 PM Phil Bouchard via Std-Discussion
<std-discussion@lists.isocpp.org> wrote:
I apologize but people forget the US government disallows memory unsafe programming languages:

https://media.defense.gov/2025/Jun/23/2003742198/-1/-1/0/CSI_MEMORY_SAFE_LANGUAGES_REDUCING_VULNERABILITIES_IN_MODERN_SOFTWARE_DEVELOPMENT.PDF

Given the importance of the problem I was hoping for a constructive discussion as it is free anyways for OSS projects.
The validity of your description of that paper aside (nothing in that
paper seems to "disallow" anything; it's just a look at the current
state of affairs), that doesn't justify your post. This ML is for
discussing the C++ standard as it exists. If you want to propose
changing it, there's a different ML for that.

Ok, which ML is that exactly?



But even this isn't a proposal. Your post has no detailed discussion
of what is being proposed; it's just an advertising blurb and a link
to another page containing advertising and the tool itself. The kinds
of details that should be present for any proposal are not immediately
present behind that link. Perhaps there are more links past that, but
I didn't bother looking.

What advertising? 

There's a video very easy in the previously mentioned link to understand and basic documentation here:

https://static.fornux.com/files/pdf/Superset_Manual.pdf

I'm working on this since the early Boost C++ library days and I figured this is the only possible solution to fix the memory management problem in a predictable way. It's better than Rust because it handles cyclic pointers, acyclic graphs of data as well and everything is handled implicitly. It is also faster than std::shared_ptr<>.


Thanks,

-Phil


In short, there's a lot of work to be done to turn whatever that tool
is into a legitimate proposal.
--
Email Signature
Fornux Logo
Phil Bouchard LinkedIn Icon
Founder & CEO
T: (819) 328-4743
E: phil@fornux.com | www.fornux.com
720 Oliver Ave, San Diego, CA, 92109
The Best Predictable C++ Memory Manager Le message ci-dessus, ainsi que les documents l'accompagnant, sont destinés uniquement aux personnes identifiées et peuvent contenir des informations privilégiées, confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce message par erreur, veuillez le détruire.
This communication (and/or the attachments) is intended for named recipients only and may contain privileged or confidential information which is not to be disclosed. If you received this communication by mistake please destroy all copies.