mrustc
rust-blog
Our great sponsors
mrustc | rust-blog | |
---|---|---|
75 | 63 | |
2,087 | 6,608 | |
- | - | |
8.8 | 5.0 | |
2 days ago | about 2 months ago | |
C++ | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mrustc
-
Why do lifetimes need to be leaky?
No, you don't. Existential proof: mrustc ignores lifetimes. Just flat out simply ignores. It changes some corner-cases related to HRBT, yet rustc compiled by mrustc works (that's BTW mrustc exist: to bootsrap the rustc compiler).
-
I think C++ is still a desirable coding platform compared to Rust
Incidentally C++ is the only way to bootstrap rust without rust today.
https://github.com/thepowersgang/mrustc
-
Rust – Faster compilation with the parallel front-end in nightly
Well, there is mrustc[0], a Rust compiler that doesn't include a borrow-checker, so it's possible to compile (at least some versions of) Rust without a borrow checker, though it might not result in the most optimized code.
AFAIK there are some optimization like the infamous `noalias` optimization (which took several tries to get turned on[1]) that uses information established during borrow checking.
I'm also not sure what the relation with NLL (non-lexical lifetimes) is, where I would assume you would need at least a primitive borrow-checker to establish some information that the backend might be interested in. Then again, mrustc compiles Rust versions that have NLL features without a borrow-checker, so it's again probably more on the optimization side than being essential.
[0]: https://github.com/thepowersgang/mrustc
[1]: https://stackoverflow.com/a/57259339
- Running the "Reflections on Trusting Trust" Compiler
-
Forty years of GNU and the free software movement
> Maybe another memory safe language, but Rust has severe bootstrapping issues which is a hard sell for distros that care about source to binary transparency.
It is possible to bootstrap rustc from just GCC relatively easily, although it's a little bit time consuming.
You can use mrustc to bootstrap Rust 1.54: https://github.com/thepowersgang/mrustc
And from then you can go through each version all the way to the current 1.72. (Each new Rust version officially needs the previous one to compile.)
-
Building rustc on sparcv9 Solaris
Have you tried this route : https://github.com/thepowersgang/mrustc ?
-
GCC 13 and the state of gccrs
Mrustc supports Rust 1.54.0 today
- Any alternate Rust compilers?
-
Stop Comparing Rust to Old C++
There are three. The official one, mrustc (no borrow checker, but can essentially compile the official rustc) and GCC (can't really compile anything substantial yet). Only rustc is production-ready though.
-
Can I make it so that only the newest version of Rust gets installed?
That probably depends on what you mean by problematic. Having an ever increasing chain of dependencies isn’t the most desirable situation so there has been some work to trim the bootstrap chain. In 2018, when the blogpost I linked above was written, mrustc was used to bootstrap rust 1.19.0; now mrustc can bootstrap rust 1.54.0 so the chain to recent versions is much shorter than if all those intervening versions back through 1.19.0 needed to be built. https://github.com/thepowersgang/mrustc
rust-blog
- Common Rust Lifetime Misconceptions
-
What are some good resources for experienced programmers new to Rust to learn about lifetimes?
Hands down the best resource (after you've had sufficient experience with Rust, especially so) - https://github.com/pretzelhammer/rust-blog/blob/master/posts/common-rust-lifetime-misconceptions.md
-
How can a parameter type `T` be not long living enough?
I really really recommend reading this to understand lifetimes and generics in Rust better.
- What learning resource has had the greatest impact in elevating your understanding and knowledge of Rust?
- I do not understand why Sized bound prevents a trait from being used as a trait object.
-
Lifetime annotations: why doesn't Rust?
It's already now that the elided lifetimes are not always correct, as pointed out in Common Rust Lifetime Misconceptions (No 5) by pretzelhammer.
-
Anything C can do Rust can do Better
Common Rust Lifetime Misconceptions - kirill
-
Resources on Lifetimes
Probably a bit more advanced than what you asked about, but still possibly useful: Common Rust Lifetime Misconceptions by /u/pretzelhammer.
-
Borrow checker puzzles
This helped me a lot understanding Rust ownership rules and lifetimes: https://github.com/pretzelhammer/rust-blog/blob/master/posts/common-rust-lifetime-misconceptions.md
What are some alternatives?
gccrs - GCC Front-End for Rust
zero-to-production - Code for "Zero To Production In Rust", a book on API development using Rust.
gccrs - GCC Front-End for Rust
fluvio - Lean and mean distributed stream processing system written in rust and web assembly.
llvm-cbe - resurrected LLVM "C Backend", with improvements
static-analysis - ⚙️ A curated list of static analysis (SAST) tools and linters for all programming languages, config files, build tools, and more. The focus is on tools which improve code quality.
rust-ttapi
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
miri - An interpreter for Rust's mid-level intermediate representation
mini-redis - Incomplete Redis client and server implementation using Tokio - for learning purposes only
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
polonius - Defines the Rust borrow checker.