Nix Rust | 671 Members | |
| Rust | 154 Servers |
| Sender | Message | Time |
|---|---|---|
| 27 Oct 2025 | ||
|
| 13:17:59 | |
| Bisected to https://github.com/NixOS/nixpkgs/pull/455250 | 13:29:19 | |
| i reccomens using crane combined with fenix, i found it great myself. perhaps fenix alone is enough for you though. | 13:52:15 | |
In reply to @quadradical:federated.nexusHow would you switch between toolchains? | 15:22:02 | |
| multiple devshells | 15:26:56 | |
| yes, would work | 18:50:07 | |
| for that fenix only is enough | 18:50:15 | |
but you can also for your unit tests, use crane with fenix, and then just use nix flake check to run your tests | 18:50:29 | |
| 20:55:00 | ||
| 28 Oct 2025 | ||
| 14:35:52 | ||
| a follow up question to yesterdays question. i use currently stable rust. because i want that every code i write to work on stable. i am only interested in unstable for things like miri and instrumentation (for test code coverage). ... when i choose nightly in my devenv i think there is only a very small chance that my code is treated differently compared to stable right? | 22:03:46 | |
| yeah, pretty much. differences in behavior are almost always either a bug (in rust) or a fix (which you'll get in a few weeks on stable, and you probably want) | 22:31:19 | |
| * yeah, pretty much. differences in behavior are almost always either a bug (in rust itself) or a fix (which you'll get in a few weeks on stable, and you probably want) | 22:31:39 | |
| * yeah, pretty much. differences in behavior are almost always either a bug (in rust itself) or a fix (which you'll get in a few weeks on stable, and you probably want) (obviously this no longer holds true when you opt into unstable features with #![feature(...)] or -Z and such, but this is true for already-stable things) | 22:34:04 | |
| thank you for clarifying | 22:39:09 | |
| 29 Oct 2025 | ||
| I switched to fenix with complete toolchain. The problem is that rustfmt (or whatever is the default for formatting) somehow doesn't recognize that the project is written in edition 2024. It fails with an error something along the line "let chains only supported in edition 2024". | 11:38:45 | |
| The editor i use is helix | 11:39:13 | |
what's your rustfmt.toml say | 14:41:13 | |
| I don't have one in the project. Are there other places where i should look? | 17:10:20 | |
Make sure which rustfmt doesn’t pick up an older rustup installation? | 17:21:22 | |
| that might be your problem. i'm not sure if rustup cares to read Cargo.toml to figure out the edition | 18:49:07 | |
| you do at least have the edition set properly in Cargo.toml, yeah? | 18:49:56 | |
| * that might be your problem. i'm not sure if rustfmt cares to read Cargo.toml to figure out the edition | 18:50:52 | |
maybe it does if you cargo fmt but not if you rustfmt, you could try both and see what happens and then check how helix is invoking the formatter | 18:51:26 | |
| Yes. I have all the expected binaries. And a cargo toml with edition 2024. And rustfmt print-config shows the wrong edition. But because i kept working it doesn't fail anymore | 18:51:49 | |
| Cargo fmt as well | 18:52:20 | |
| At least i know now what i should configure if i run into the problem again. Should not be nix specific | 18:53:18 | |
| 30 Oct 2025 | ||
| 19:10:31 | ||
| 31 Oct 2025 | ||
| 01:55:33 | ||
| 11:57:33 | ||