libs-team VS awesome-rust

In rust, both release and debug builds use a release version of the runtime. The bugs the debug version is meant to catch are much more difficult to hit in rust (often but not always requiring unsafe). There isn't currently a feature to use the debug runtime in rust-- you can only change C to match for those debug builds.

Note that this has been discussed at length (and I do mean "at length") here: https://github.com/rust-lang/libs-team/issues/72

The Compiler Team, especially the Diagnostics Working Group that improves compiler error messages. The Libs Team, for work on the contents of the standard library documentation

See https://github.com/rust-lang/libs-team/issues/72#issuecommen... for what I believe is an exhaustive list of possible ways of helping the situation.

The point is how the MSRV of a popular crate affects this dynamic for other crates. For an even more extreme example than time, see here for libc, with many heavyweights offering opinions: https://github.com/rust-lang/libs-team/issues/72

In case you haven't seen it yet, there is a very long discussion surrounding MSRV policy of the libc crate on rust-langs github repo. It's about a library, not a binary, but I think there's a lot of information in the thread, some of which will also apply to binaries.

Would you mind sharing your use case for being stuck with a particular version of Rust and why you can't upgrade? In particular with the libs team: https://github.com/rust-lang/libs-team/issues/72

Compare Stepanov's brilliant design of the STL to Rust's current reworking of their 'binary search api'. https://github.com/rust-lang/libs-team/issues/81

Maybe 'memory safety' isn't the most important thing in this world. To me, writing software that does useful things in the simplest and most correct way is what matters. I get the feeling it's harder to understand my program's correctness with Rust (I mean algorithmic correctness). The C++ standard library has time and space complexity for every algorithm. I'm not seeing that's the case with Rust (correct me if I'm wrong).

There's also the pretty fundamental libc crate that wants to choose an MSRV policy and you can see the full discussion here: https://github.com/rust-lang/libs-team/issues/72

It can be tricky to find learning resources that is perfectly tailored to the exact point we’re you’re standing right now. Especially if you already have prior experience.

But since you’re already familiar with programming, perhaps just dive right in…?

I.e. start a new project in Rust. You could do something like Advent of Code, Project Euler or Cryptopals[0]. Or write a simple webserver or whatever you feel like.

Don’t forget that ChatGPT can be quite useful for stuff like this. You can use it like a mentor. Just ask it anything you want to, make it show you examples (and then more examples) and so on. The answers might not be correct all of the time, but at least it can give you an idea of what docs to read next.

If you’re looking for blog posts, an acquaintance of mine has written some: https://priver.dev/tags/rust/

For more links to code/learning resources, see https://github.com/rust-unofficial/awesome-rust

And if you get stuck you also have the official Rust chats on Zulip/Discord.

HTH. Best of luck!

[0] https://cryptopals.com/

View on GitHub

I did find the official https://doc.rust-lang.org/book/ quite useful, it's more than enough to understand the language itself. Command-line programing is not a complicated thing, basically you have the CLI arguments, environment variables, stdin-stdout-sterr and nothing else. A few crates to start with: clap, dotenv, config, log4rs. Just go the crate documentation, there are many good examples there, no other book is neccessary. If you have a specific problem to solve, start to browse crates.io or https://github.com/rust-unofficial/awesome-rust for possible solutions.

37. Awesome Rust is a great repo with a huge curated list of plenty with Rust code and resources. You can find complete applications in different areas that were built based on Rust.

Post it there https://github.com/rust-unofficial/awesome-rust

I'd recommend taking a look at https://github.com/rust-unofficial/awesome-rust and seeing if anything interests you that way.

Not really sorted by complexity, but awesome-rust might be close to what you're looking for.

See also:

https://github.com/rust-unofficial/awesome-rust

This list is currently far more comprehensive, and it's filled with a lot of high-quality crates.