Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
creusot
Discontinued Creusot helps you prove your code is correct in an automated fashion. [Moved to: https://github.com/creusot-rs/creusot] (by xldenis)
-
rustris
A no-frills Tetris implementation written in Rust with the Piston game engine, and Rodio for music.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Clippy
A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
Actual serious answer: https://www.rust-lang.org/ It’s a systems programming language that focuses on correctness and safety.
As I think this is a serious question, the answer is both a yes and a no. Currently you'd be unable to only compile it with GCC, but there's work to have a GCC rust front end and a GCC backend for rustc. So, you'll be able to just use GCC, but not yet. Which should answer your second question. Also, note that rust is only accepted as a way to write kernel tree leafs, and maybe it'll be upgraded to be used everywhere.
Easy reasoning does not end on memory safety. For example, deductive verification of Rust code is possible exactly because there's no reference aliasing in safe Rust
As I think this is a serious question, the answer is both a yes and a no. Currently you'd be unable to only compile it with GCC, but there's work to have a GCC rust front end and a GCC backend for rustc. So, you'll be able to just use GCC, but not yet. Which should answer your second question. Also, note that rust is only accepted as a way to write kernel tree leafs, and maybe it'll be upgraded to be used everywhere.
https://github.com/bwcpub/rustris for the code and etc