| 8 Sep 2024 |
 olk | yes | 11:05:48 |
 K900 | Then you should probably not do that | 11:07:21 |
| K900 | And report the issue upstream | 11:07:24 |
| olk | In reply to @k900:0upti.me
And report the issue upstream ah, do it's not a nix thing? | 11:07:50 |
| olk | In reply to @k900:0upti.me
Then you should probably not do that I need the nightly toolchain to build std | 11:08:08 |
| K900 | It is not a nix thing | 11:08:23 |
| K900 | And you do not need to build std | 11:08:28 |
| olk | probably, but I want the executable to be small. I don't need it, I want it
| 11:09:21 |
| olk | In reply to @k900:0upti.me
It is not a nix thing ok, then I'll report this upstream. thanks | 11:09:35 |
| 9 Sep 2024 |
|  Pandapip1 joined the room. | 03:43:32 |
 ˈt͡sɛːzaɐ̯ | In reply to @k1gen:matrix.org
probably, but I want the executable to be small. I don't need it, I want it
You could use an older nightly, or make a release version predend it's a nightly with the right flags. | 05:17:03 |
| olk | why isn't
devShells.default = craneLib.devShell {
toolchain = fenix.packages.${system}.default.toolchain;
};
installing neither clippy nor rustfmt?
| 09:27:34 |
| K900 | Because those aren't part of the default toolchain? | 09:30:37 |
| olk | The default profile includes all of components in the minimal profile, and adds rust-docs, rustfmt, and clippy. This profile will be used by rustup by default, and it’s the one recommended for general use.: https://rust-lang.github.io/rustup/concepts/profiles.html | 09:32:23 |
| olk | toolchain = fenix.packages.${system}.complete.withComponents [ "cargo" "clippy" "rust-src" "rustc" "rustfmt" ]; doesn't work as well | 09:36:09 |
|  declension joined the room. | 16:04:03 |
 cafkafk | iirc crane does include those | 17:05:50 |
| cafkafk | ¯\_(ツ)_/¯ | 17:05:54 |
| cafkafk | idk may be hallucinating, I have something like this
craneLibLLvmTools = craneLib.overrideToolchain (
fenix.packages.${system}.complete.withComponents [
"cargo"
"llvm-tools"
"rustc"
]
);
| 17:06:51 |
| cafkafk | you shouldn't need to specify the toolchain in the craneLib.devShell either I think | 17:08:04 |
| cafkafk | https://crane.dev/API.html?highlight=craneLib.dev#cranelibdevshell
Note that the current toolchain's cargo, clippy, rustc, and rustfmt packages will automatically be added to the devShell.
| 17:08:12 |
|  Enric Morales joined the room. | 17:41:36 |
|  Lulu joined the room. | 20:31:33 |
| 10 Sep 2024 |
|  @adis:blad.is left the room. | 09:42:36 |
|  (artur 'manuel) changed their display name from (lambda (u) (format nil "~A lost their email!" u)) "Artur Manuel" to Artur Manuel (on break). | 17:32:11 |
| (artur 'manuel) changed their profile picture. | 17:34:33 |
| (artur 'manuel) changed their display name from Artur Manuel (on break) to (lambda (u) (format nil "~A is not using Matrix right now." u)) "Artur Manuel". | 17:36:12 |
 Theo Paris | Am I correct that the only way to patch rustc outside of nixpkgs is to copy pkgs/development/compilers/rust/1_80.nix outside of nixpkgs to override rustcPatches? | 20:20:12 |
| Theo Paris | * Am I correct that the only way to patch rustc outside of nixpkgs is to copy pkgs/development/compilers/rust/1_80.nix toverride rustcPatches? | 20:20:20 |
| Theo Paris | * Am I correct that the only way to patch rustc outside of nixpkgs is to copy pkgs/development/compilers/rust/1_80.nix to override rustcPatches? | 20:20:29 |
