Skip to content

introduce rust toolchain to nix#28

Open
mightyiam wants to merge 1 commit intoNixOS:mainfrom
mightyiam:introduce-rust-toolchain-into-nix
Open

introduce rust toolchain to nix#28
mightyiam wants to merge 1 commit intoNixOS:mainfrom
mightyiam:introduce-rust-toolchain-into-nix

Conversation

@mightyiam
Copy link
Contributor

No description provided.

Copy link
Contributor

@tomberek tomberek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs more detail. Prior art is snix/tvix? @RossComputerGuy is working on eval? We've talked about the Store layer being appropriate for Rustification as it is way simpler than the language layer.

@Eveeifyeve
Copy link
Member

I am already starting a rewrite here: https://github.com/DigitalBrewStudios/rust-nix my aim is starting with the eval which has many benefits than the store layer.

Copy link
Member

@piegamesde piegamesde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I fear like this project would be nothing but setting up some poor intern up for failure. Pulling this off successfully would at the very least require some intense amounts of preparation and mentoring from deeply experienced people in the code base. Even seemingly simple and contained tasks like "get Rust<->C++ interop to work" can quickly turn into nightmares of debugging deep internals of build systems and linkers.

I am already starting a rewrite here: https://github.com/DigitalBrewStudios/rust-nix

Am I missing something or are there no commits? I don't think pressing "fork" and renaming the repo is a noteworthy feat, and given "starting with the eval" I must assume that this is a very naive and uninformed statement that has yet to make first contact with the harsh reality that is this code base.

Image

@Eveeifyeve
Copy link
Member

Eveeifyeve commented Feb 21, 2026

I fear like this project would be nothing but setting up some poor intern up for failure. Pulling this off successfully would at the very least require some intense amounts of preparation and mentoring from deeply experienced people in the code base. Even seemingly simple and contained tasks like "get Rust<->C++ interop to work" can quickly turn into nightmares of debugging deep internals of build systems and linkers.

100%, I was going to mention this, It doesn't seem that GSOC would be appropriate for this kinda of work.

Am I missing something or are there no commits? I don't think pressing "fork" and renaming the repo is a noteworthy feat, and given "starting with the eval" I must assume that this is a very naive and uninformed statement that has yet to make first contact with the harsh reality that is this code base.
Image

Sorry I should have rephrased it, beginning to rewrite parts of nix in rust. So we are starting to get cpp -> rust interup working correctly and hooked up with meson for lib-expr-rs eval, while thinking about the benefits of what rust could bring to the table. I haven't pushed any changes but I have made an announcement publicly on our discord, we are going to work on this.

@RossComputerGuy
Copy link
Member

As @tomberek mentioned, I've been working on my own implementation. It is far from complete and not fully functional yet.
https://github.com/RossComputerGuy/yani

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants