Rust support coming to GCC

Like here's Rust's String class:

https://doc.rust-lang.org/std/string/struct.String.html

We get a discussion of the features, mentioning that Deref<Target=str> (ie you can use a String almost anywhere &str would work), explaining about UTF-8, how String works (e.g. capacity) and so on, we get a break down of all the methods on String, (and on &str because of the Deref I mentioned) with examples in many cases you can play with straight from your browser and links to the actual implementation of these features in fairly readable Rust.

Now here's the closest CPP Reference gets us:

https://en.cppreference.com/w/cpp/string/basic_string

That's a pretty intimidating wall of text, and it's that way because CPP Reference documents all C++ versions, which of course are incompatible, and so stuff appeared or disappeared in different versions and there are numerous exceptions, and the exceptions to those exceptions, as a result. It's also that way because C++ has a tremendous number of "string" types documented here.

We need to guess what we might be interested in and drill into individual methods like contains() to get to examples we can try, and so those examples can't realistically help us explore this type.

Maybe it's unfair to focus on Strings, since although they're a common idea C famously can't get them right so why should C++. Lets try a more fundamental type, char:

https://doc.rust-lang.org/std/primitive.char.html

versus

https://en.cppreference.com/w/cpp/language/types#Characte...

Wow, C++ even manages to have lots of char types. Of them char32_t is the closest to usable. But, I happen to know this documentation isn't sparse by mistake, these types just don't have any features. In C they wouldn't be able to have features and so perhaps out of perverse solidarity, they have no features in C++ either. As you can see the Rust char type has methods, constants, associated functions, and implements a bunch of traits.

Furthermore though, Rust provides documentation in this same style automatically for your own libraries. Here's the documentation for my LoadLetter type, which is an implementation of two I/O traits which just always fails.

https://docs.rs/misfortunate/1.0.0/misfortunate/struct.Lo...

So far as I can tell, if I write some C++ I don't get a CPP Reference page for it.

Fundamental concepts from Unsafe Rust could do with more documentation, but the vast majority of a team's effort and of most programmer's time will be spent with safe Rust, for which in my opinion Rust's documentation is in better shape than CPP Reference.