Date: Tue, 14 Feb 2023 19:11:39 -0500
On 2/14/23 18:14, Bjorn Reese via Std-Proposals wrote:
> On 2/14/23 18:02, Roberto R via Std-Proposals wrote:
>
>> Is it possible to make C++ a memory safe language? For sure it is
>> possible to make it safer, at least for new code that does not use
>> legacy code.
>
> There is a lot of experimentation going on:
>
> https://github.com/carbon-language/carbon-lang
This is exactly what I was looking for actually. Instead of revamping
C++, let's properly design a new language inheriting from C++.
> https://www.val-lang.dev/
>
> On 2/14/23 18:02, Roberto R via Std-Proposals wrote:
>
>> Is it possible to make C++ a memory safe language? For sure it is
>> possible to make it safer, at least for new code that does not use
>> legacy code.
>
> There is a lot of experimentation going on:
>
> https://github.com/carbon-language/carbon-lang
This is exactly what I was looking for actually. Instead of revamping
C++, let's properly design a new language inheriting from C++.
> https://www.val-lang.dev/
>
-- Logo <https://www.fornux.com/> *Phil Bouchard* facebook icon <https://www.linkedin.com/in/phil-bouchard-5723a910/> CTO T: (819) 328-4743 E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com> 8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada Banner <https://goglobalawards.org/> 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.
Received on 2023-02-15 00:11:40