| 12 Feb 2026 |
|  sckova (alt) joined the room. | 15:21:19 |
| sckova (alt) changed their display name from sckova to sckova (he/him). | 15:24:36 |
|  amadaluzia changed their profile picture. | 17:48:01 |
| amadaluzia changed their profile picture. | 17:48:39 |
| amadaluzia changed their profile picture. | 17:51:25 |
| amadaluzia changed their profile picture. | 17:51:43 |
| amadaluzia changed their profile picture. | 18:00:12 |
| sckova (alt) changed their display name from sckova (he/him) to sckova (alt). | 20:02:41 |
|  llang joined the room. | 23:00:57 |
| 13 Feb 2026 |
|  hoplopf joined the room. | 10:19:53 |
|  @lengorbital:matrix.org removed their profile picture. | 18:48:26 |
| @lengorbital:matrix.org removed their display name klbr-l0673. | 18:48:41 |
| @lengorbital:matrix.org left the room. | 18:49:05 |
| 14 Feb 2026 |
 Logan Devine | proc-macro panicked: failed to load macro: Cannot create expander for /Users/logandevine/Documents/zr/zirco-playground/api-server/target/debug/deps/libtokio_macros-f10cf80816e839ef.dylib: mismatched ABI expected: `rustc 1.95.0-nightly (47611e160 2026-02-12)`, got `rustc 1.92.0-nightly (695857bc3 2025-10-21)`rust-analyzermacro-error
Anyone have issues with VSCode's rust-analyzer on Nix in VSCode? I have a direnv set to use the flake, with the Rust I want to use installed, and vscode runs the extensions with it too. But yet, it seems to be a version mismatch, even with all my testing telling me they're both 1.95
| 04:36:39 |
| Logan Devine | I tried enabling the RA feature in my flake and telling vscode to use that rust-analyzer instead, still to no avail.. :/ | 04:37:10 |
 catbrained (she/her) | No clue, but did you try to do a cargo clean and rebuild everything from scratch? | 14:01:48 |
| Logan Devine | Dozens of times. This has been happening for days. It makes my editor almost unusable haha
Also it seems to recompile dependencies every time I run cargo build, so there's definitely a second compiler version in there...
| 14:03:00 |
| catbrained (she/her) | Hmm, uhh I think cargo/rustc might put metadata in the built artifacts.
Does that contain something useful to find the culprit? | 14:05:47 |
| Logan Devine | Hm, good idea | 14:08:25 |
 Ben Sparks | In reply to @logn:zirco.dev
proc-macro panicked: failed to load macro: Cannot create expander for /Users/logandevine/Documents/zr/zirco-playground/api-server/target/debug/deps/libtokio_macros-f10cf80816e839ef.dylib: mismatched ABI expected: `rustc 1.95.0-nightly (47611e160 2026-02-12)`, got `rustc 1.92.0-nightly (695857bc3 2025-10-21)`rust-analyzermacro-error
Anyone have issues with VSCode's rust-analyzer on Nix in VSCode? I have a direnv set to use the flake, with the Rust I want to use installed, and vscode runs the extensions with it too. But yet, it seems to be a version mismatch, even with all my testing telling me they're both 1.95
Silly question, but what does your path / (dev)shell.nix look like? | 18:06:04 |
| Ben Sparks | * Silly question, but what does your $PATH / (dev)shell.nix look like? | 18:13:31 |
| Logan Devine | https://github.com/zirco-lang/zrc/blob/main/flake.nix | 18:13:32 |
| Logan Devine | The metadata agreed the rustc version I thought was what seemed to be building but idk how that affects cargo check or the RA server | 18:13:58 |
| Logan Devine | I previously didn't add the rust-analyzer feature because it worked until recently with no change afaik | 18:14:30 |
| Ben Sparks | echo $PATH in vscode, check that your settings.json isn't doing odd thing etc. | 18:14:53 |
| Ben Sparks | Use direnv and point it at your flake.{nix,lock} | 18:15:32 |
| Logan Devine | Nothing special about it in my settings afaik, I'll check the PATH when I get home. I use direnv, both the VSCode extension and for my shells | 18:16:16 |
| Ben Sparks | You can also try to provide cargo and rust from the overlay, by pointing them at variables given by rust-overlay :) there's a lot to try here, so I think you'll find something | 18:18:05 |
| Logan Devine | hopefully yea, i'll give it a try | 18:26:59 |
| Logan Devine | Using rustup rust-analyzer in contrast to rust-bin appears to work | 18:58:10 |
