rust-how-do-i-start VS gccrs

For (1) try this https://github.com/jondot/rust-how-do-i-start

I learned it combining the Book and Rustlings. There's a table in the exercises directory mapping the exercises to the chapters of the book, so I'd every day do the exercises for yesterdays chapter first before todays chapter to have some sort of spaced repetition. For more material, check out https://github.com/jondot/rust-how-do-i-start

You can try https://github.com/jondot/rust-how-do-i-start which contains things to try out that I've curated. Cross off things that don't work, and feel free to reach out if none of it work for you.

I highly recommend taking a look at this github repo, it has many projects and resources to help you!

Rustlings is great. I did them after a couple of years in Rust for the same reason, and it was definitely worth it. You might want to check out https://github.com/jondot/rust-how-do-i-start as well where I put all these kind of things that I could find.

If you aren't a complete beginner, then this github repo is VERY useful

This is mine but also incorporates things I wish I had when I started, and also recommendation from other people as well. https://github.com/jondot/rust-how-do-i-start

This was posted this week here: https://github.com/jondot/rust-how-do-i-start

There is a Rust front-end for GCC that is under active development [1]. If the chip vendors are not willing to develop and upstream a LLVM back-end then they can feel free to start contributing to it.

[1] https://rust-gcc.github.io/

That's why gccrs doesn't even consider lifetime checking a part of the language (they plan to use Polonius, too).

There's ongoing work on a Rust front-end for GCC (https://github.com/Rust-GCC/gccrs). Bit barebones right now -- ie, even core doesn't compile -- but there's funding, demand, and regular progress, so it'll only get better from there. Once gccrs can compile core, it should be ready to compile most of Rust, and thus if you've taught the calling conventions for C to GCC, you're golden.

I recommend checking out the GCC Rust frontend project.

That is what theyre refering to, yes. The GitHub is named https://github.com/Rust-GCC/gccrs

- But this misses so much extra context information

3. Macro invocations there are really subtle rules on how you treat macro invocations such as this which is not documented at all https://github.com/Rust-GCC/gccrs/blob/master/gcc/rust/expan...

Some day I personally want to write a blog post about how complicated and under spec'd Rust is, then write one about the stuff i do like it such as iterators being part of libcore so i don't need reactive extensions.

(Speaking of which, Rust-GCC (or gcc-rs or gccrs or whichever other of their names they decide is the primary one) isn't even going to be a complete C++ implementation. Their plan is to implement enough to compile Polonius (the NLL 2.0 borrow checker being developed in Rust for rustc) and then share that since borrow-checking isn't necessary for codegen... only to identify and reject invalid programs... making the C++ portion of it not that different in scope from mrustc.)

That bridge will be crossed with gccrs (compiling Rust with gcc directly, coming next month with GCC 13) and rust_codegen_gcc (rustc frontend, GCC backend, works now but just doesn’t yet have an “easy” setup)