Shulou(Shulou.com)06/01 Report--

This article mainly introduces "C++ rust safety rule example analysis", in daily operation, I believe many people in C++ rust safety rule example analysis problems have doubts, Xiaobian consulted all kinds of information, sorted out simple and easy to use operation methods, hope to answer "C++ rust safety rule example analysis" doubts helpful! Next, please follow the small series to learn together!

Microsoft implements some of Rust's security rules in C++ static analysis tools Rust and C++ are two popular systems programming languages. For years, C++ has focused on performance. We are increasingly hearing calls from customers and security researchers that the C++ language should have stronger security guarantees. Visual Studio 2019 version 16.7 includes four new rules in C++'s core checks to incorporate some of Rust's security features into C++.

Path trimming in Nightly Rust This Rust PR (which I'm doing) is incorporated into Rust nightly, which has a wide impact on compiler errors. The problem with the complete path in errors: A simple procedure like the one shown below will result in type errors. fn main() {

let a = vec! [vec! [String::from("a")]];

let b = vec! [String::from("b")];

a == b;

}

Type errors can be described as: cannot compare between values of the types Vec and Vec. This is almost the first line of error messages before PR changes, and the rest of the error messages provide more details about the features: error[E0277]: can't compare `std::vec::Vec` with `std::string::String`

--> example.rs:5:7

|

5 | a == b;

| ^^ no implementation for `std::vec::Vec == std::string::String`

|

= help: the trait `std::cmp::PartialEq` is not implemented for `std::vec::Vec`

= note: required because of the requirements on the impl of `std::cmp::PartialEq` for `std::vec::Vec`

Notably, among the errors described above, the largest contributor to cognitive burden is the complete qualified path for type and feature (e.g. std::vec:: vec). For many people, its readability makes a big difference. At this point, the study of "C++ rust security rule example analysis" is over, hoping to solve everyone's doubts. Theory and practice can better match to help everyone learn, go and try it! If you want to continue learning more relevant knowledge, please continue to pay attention to the website, Xiaobian will continue to strive to bring more practical articles for everyone!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.