pegasust/dotfiles
1
0
Fork 0
Code Issues 6 Pull Requests Projects Releases Wiki Activity

Rust: Rust-analyzer (devShell?) + Neovim + bacon is not playing well. #12

New Issue
Open
opened 2023-03-02 02:45:06 +00:00 by pegasust · 2 comments
pegasust commented 2023-03-02 02:45:06 +00:00
Owner
Copy Link

Currently we need to do cargo clean, bacon test in order to create good /target.

  • Rust-analyzer seems fine with bacon test and not entirely with cargo build
  • Rust-analyzer uses cargo metadata, which overwrites Cargo.toml in the rustc/cargo. These runtimes live in /nix/store, so they're read-only, which makes rust-analyzer fail.
Currently we need to do `cargo clean`, `bacon test` in order to create good `/target`. - Rust-analyzer seems fine with `bacon test` and not entirely with `cargo build` - Rust-analyzer uses `cargo metadata`, which overwrites `Cargo.toml` in the `rustc`/`cargo`. These runtimes live in `/nix/store`, so they're read-only, which makes rust-analyzer fail.
pegasust commented 2023-03-02 03:12:42 +00:00
Author
Owner
Copy Link

As an attempt to synchronize Rust version everywhere, we'll migrate many projects to use nix-boost instead. Hence, this is related to #11. nix-boost will take care of providing:

  • rust4cargo: The most barebone rustc install possible
  • rust4devs: Dev-friendly rustc install
  • rust4normi: Recommended install for everyone, basically refers to the default toolchain
  • rust-dev-env: My own dev environment. At the time of writing, it's rust4devs with excvr and bacon.
As an attempt to synchronize Rust version everywhere, we'll migrate many projects to use `nix-boost` instead. Hence, this is related to #11. `nix-boost` will take care of providing: - `rust4cargo`: The most barebone rustc install possible - `rust4devs`: Dev-friendly rustc install - `rust4normi`: Recommended install for everyone, basically refers to the default toolchain - `rust-dev-env`: My own dev environment. At the time of writing, it's `rust4devs` with `excvr` and `bacon`.
pegasust commented 2023-08-02 01:59:38 +00:00
Author
Owner
Copy Link

after having std as a framework, devshell is a bit tough #19 addresses this.

At the moment, we do have a lot of these implemented in nix-boost

296de75f05/cells/dev/devshells.nix (L7-L81)

Note that this implementation is being gated harshly by numtide/devshell#266

after having `std` as a framework, `devshell` is a bit tough #19 addresses this. At the moment, we do have a lot of these implemented in `nix-boost` https://git.pegasust.com/pegasust/nix-boost/src/commit/296de75f052d88880414a72c6df6fe3b6a3f603d/cells/dev/devshells.nix#L7-L81 Note that this implementation is being gated harshly by [numtide/devshell#266](https://github.com/numtide/devshell/pull/266)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: pegasust/dotfiles#12
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?