{"id":116100,"date":"2024-05-26T22:54:55","date_gmt":"2024-05-26T20:54:55","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-kazhdom-pyatom-pakete-na-yazyke-rust-ispolzuetsya-rezhim-unsafe"},"modified":"2024-05-26T22:54:55","modified_gmt":"2024-05-26T20:54:55","slug":"v-kazhdom-pyatom-pakete-na-yazyke-rust-ispolzuetsya-rezhim-unsafe","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-kazhdom-pyatom-pakete-na-yazyke-rust-ispolzuetsya-rezhim-unsafe","title":{"rendered":"One in five packages in the Rust language uses the unsafe mode","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The Rust Foundation has published statistics indicating that out of 127,000 significant packages listed in the crates.io directory, over 24,000 (19.11%) use the keyword 'unsafe' to enable functionalities that allow unsafe operations with memory in specific blocks of code, such as dereferencing pointers, calling external functions, or modifying static variables. 34.35% of packages make direct calls to functions from other crate packages that employ 'unsafe' mode. <\/p>\n
It is noted that in most cases, the use of 'unsafe' mode is due to calling code written in other languages or accessing libraries in C\/C++. The package with the highest number of calls in 'unsafe' mode is the windows crate package developed by Microsoft, which serves as a wrapper for the Windows platform API. This package has recorded 36 million downloads. Unsafe mode is also used in the most popular packages syn (470 million downloads), proc-macro2 (354 million downloads), and libc (345 million downloads). <\/p>\n
To identify issues in code executed in 'unsafe' mode, the Miri interpreter is being developed as part of the project. This tool allows detecting accesses beyond buffer boundaries, use of memory after it has been freed, incorrect use of uninitialized data, violations of basic type invariants (for example, a bool not corresponding to the values 0 or 1), violations of ownership rules, the occurrence of race conditions, and memory leaks. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"