Hi Phil, if your approach is proprietary and patented, then there is room for other approaches. And perhaps yours does not cover all requirements one could have. E.g. does it cover all memory bugs at compile-time?   Especially one needs solutions for each architectural layer. It is not enough to compile a language with a safe C++ to prevent any bugs inside that other language.   -----Ursprüngliche Nachricht----- Von:Phil Bouchard via Std-Proposals <std-proposals_at_[hidden]> Gesendet:Di 03.06.2025 02:50 Betreff:Re: [std-proposals] Memory Safety in C++ via Safe Subset and Static Analysis - Master’s Thesis Summary An:std-proposals_at_[hidden]; CC:Phil Bouchard <boost_at_[hidden]>; On 6/1/25 04:32, Thomas Krogh Lohse via Std-Proposals wrote: > > I’d love to hear your thoughts: >      * Do you see value in defining a "safe-by-default" C++ subset with > opt-in unsafe features? >      * Could something like this analysis model help enforce safety in > future directions for the language? Excellent idea but I already wrote a patented deterministic memory manager injected at compile-time using a source-to-source compiler: https://github.com/philippeb8/root_ptr So you basically don't have anything to do other than running the compiler over existing C/C++ code and you'll have an executable as fast as the original source. Furthermore, since Python and Java are all ultimately written in C, it can also be extended for these languages. > > I’ve tried to keep this short, but I’d be happy to elaborate on any part > of the project if there's interest. Initially I thought this would be a very simple project but it took me more than 10 years to complete the memory manager and 5 years to complete the source-to-source compiler given all the complexity of the C++ language. But I'm a step away from successfully compiling complex libraries like OpenCV. > > Best regards, > Thomas Lohse > -- Fornux Logo <https://www.fornux.com/> *Phil Bouchard* LinkedIn Icon <https://www.linkedin.com/in/phil-bouchard-5723a910/> Founder & CEO T: (819) 328-4743 E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com> 320-345 de la Gauchetière Ouest| Montréal (Qc), H2Z 0A2 Canada The Best Predictable C++ Memory Manager <https://static.fornux.com/c-superset/> 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. -- Std-Proposals mailing list Std-Proposals_at_[hidden] https://lists.isocpp.org/mailman/listinfo.cgi/std-proposals