{"id":119844,"date":"2024-09-17T15:43:07","date_gmt":"2024-09-17T13:43:07","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/c-alliance-prodvigaet-v-c-mehanizmy-bezopasnoj-raboty-s-pamyatyu-oprobovannye-v-rust"},"modified":"2024-09-17T15:43:07","modified_gmt":"2024-09-17T13:43:07","slug":"c-alliance-prodvigaet-v-c-mehanizmy-bezopasnoj-raboty-s-pamyatyu-oprobovannye-v-rust","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/c-alliance-prodvigaet-v-c-mehanizmy-bezopasnoj-raboty-s-pamyatyu-oprobovannye-v-rust","title":{"rendered":"The C++ Alliance promotes memory safety mechanisms in C++, tested in Rust.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The president of the C++ Alliance has announced the work on a specification that adds extensions for safe memory handling in the C++ language, reminiscent of features implemented in Rust. For this project, Sean Baxter, the author of the experimental C++ compiler Circle, which develops ideas to enhance C++ code safety without using garbage collection, has been involved. As part of the project, Sean published a document analyzing the applicability of various protective measures proposed in Rust, evaluating their implementation for C++, and suggesting enhancements to the C++ language to improve code safety. <\/p>\n
It is noted that the initiative was launched in response to the growing need among developers for secure programming methods, aiming to integrate new capabilities into the C++ language that can protect against common memory-related errors, such as accessing freed memory and buffer overflows. The enhancements are being developed as options that will allow projects to gradually transition to secure methods while maintaining compatibility with existing 'unsafe' code. <\/p>\n
Memory safety is proposed to be ensured through mechanisms implemented at the compilation stage that do not incur the additional overhead typical of languages that use garbage collectors. The main proposed safety methods include tracking ownership of objects, variable borrowing checks (borrow checker), the use of a safe context, and the creation of std2::send and std2::sync interfaces. The work also covers the creation of a safe version of the standard library that offers implementations of algorithms and data structures for safe memory operations. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"