rust-by-example VS gccrs

Rust can feel a bit intimidating at first but once you start getting the hang of it, you will enjoy it a lot. It has a very well articulated documentation, which can be used as a good learning resource too. Some other resources for Rust include Rustlings and Rust-By-Example.

Rust by Example

Rust by Example: Collection of runnable examples, which many find useful to read

I think something went wrong there, I can find this (merged) PR with https://github.com/rust-lang/rust-by-example/pull/1679/files that has the first example collecting into a string, (which is obv less effective). It was merged 2 weeks ago. I dont know why it isnt online yet.

I more or less went straight from The Book (see also Rust by Example) to Learning Rust With Entirely Too Many Linked Lists and code::dive conference 2014 - Scott Meyers: Cpu Caches and Why You Care and I've often seen PNGme suggested as the next step after that.

Context around the "rust by example" discussion from 2015: https://github.com/rust-lang/rust-by-example/issues/390

The Rust By Example website is another helpful resource for learning Rust. It provides a series of interactive examples that demonstrate how to use various Rust features and libraries.

The book is great and was my original introduction to the language, but rustlings or Rust By Example might be more interesting for an interactive (and more self paced) approach.

Rust by Example: Rust by Example is a collection of runnable examples that cover a wide range of Rust concepts and standard libraries. It's a great way to see how Rust code works in practice.

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)