mrustc
polonius
Our great sponsors
mrustc | polonius | |
---|---|---|
75 | 31 | |
2,083 | 1,249 | |
- | 2.7% | |
9.0 | 0.0 | |
8 days ago | 7 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
polonius
-
Why do lifetimes need to be leaky?
Correctness prover which uses lifetimes (Polonius).
-
Databases are the endgame for data-oriented design
And, well, polonius (Rust borrow checker magic) I believe is built on datalog-ish concepts: https://github.com/rust-lang/polonius
-
Why doesn't rust-analyzer reuse infrastructures of rustc?
There is also polonius (https://github.com/rust-lang/polonius) which should replace the borrow checker but does not receive a lot of development resources.
-
Rust front-end merged in GCC trunk
This is eventually going to be a feature-complete compiler, targeting a specific rustc version. I believe the plan is to use polonius [1], presumably as an "optional" feature so they can build a stage 1 without it, use that to build polonius, then build the final compiler with it included.
[1] https://github.com/rust-lang/polonius
-
Blog post: Rust in 2023
E.g. there you may just stop using current borrow-checker and switch to Polonius.
-
What are Rust’s biggest weaknesses?
The borrow checker is too dumb (https://github.com/rust-lang/polonius) fixes a lot of this.
-
Datafrog: A lightweight Datalog engine in Rust
It looks like an official borrow checker implementation called Polonius uses it as a dependency, so it makes sense: https://github.com/rust-lang/polonius/blob/981785c101b68ff54...
-
Differential Datalog: a programming language for incremental computation
If you click around a little, you end up on a blog post with this tidbit:
> This project got put together rather suddenly, in response to some work the Rust folks are doing[1] on their new and improved borrow checker.
I don't think I could tell you more than "Frank wrote it to help rust folks who were previously doing work with differential-dataflow directly."
1. https://github.com/rust-lang/polonius/pull/36#issuecomment-3...
-
Generic associated types to be stable in Rust 1.65
Good news is that there's also works going on to relax the restrictions, like polonius. But it seems that it still have a long way to go before it can land in stable Rust...
-
Rust for Linux officially merged
GCC-rs isn't intended for bootstrapping, it is intended to be an actual fully featured Rust compiler in the future, mrustc is a Rust compiler intended for bootstrapping though. GCC-rs is still very early targeting an older version of the reference compiler without things like a borrow checker, but that's not going to be the case forever. The GCC-rs folks have expressed interest in re-using the borrow checker library used by the reference compiler called polonius enabling them to relatively easily add borrow checking.
What are some alternatives?
gccrs - GCC Front-End for Rust
chalk - An implementation and definition of the Rust trait system using a PROLOG-like logic solver
gccrs - GCC Front-End for Rust
rfcs - RFCs for changes to Rust
llvm-cbe - resurrected LLVM "C Backend", with improvements
rust-ttapi
rustc_codegen_gcc - libgccjit AOT codegen for rustc
miri - An interpreter for Rust's mid-level intermediate representation
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
rust-blog - Educational blog posts for Rust beginners