News for hackers. Stuff that matters.
Re:Show HN: Fleet – Experimental build tool for Rust that’s ... by vladvasiliu on Saturday April 23, 2022 @09:52AM (#31134274)
> It also uses ramdisk on WSL or for those who use hard-drives for builds.

Yeah, I skipped over this, considering that most people doing rust dev will likely have some kind of SSD.

I didn't look into how you went about doing this, but one thing that I'd like is to be able to move the target/ directory on a ram disk, or, generally, out of the source root [0]. If Fleet were able to do this transparently, it would be really great.

---

[0] I know it's possible to define an external directory, but it applies to all projects, and it's not what I want, because shared crates would go overwrite each other.

Re:Show HN: Fleet – Experimental build tool for Rust that’s ... by VarunPotti on Saturday April 23, 2022 @10:02AM (#31134361)
Yep we also create a unique id for each project so that you can run 2 different rust apps during the same session, or else 1 rust projects build files would be mixed with the others how we go about this is we create a directory /dev/shm/<uuid> and symlinking this created directory into the rust projects target dir
Re:Show HN: Fleet – Experimental build tool for Rust that’s ... by vladvasiliu on Saturday April 23, 2022 @10:09AM (#31134405)
Do you think this could be somehow integrated with Cargo to be run with `cargo build`?

The reason I'm asking is that I use the IntelliJ plugin for Rust dev which is kind of clunky and only understands a few commands as being "build", so it doesn't show the build window.

Re:Show HN: Fleet – Experimental build tool for Rust that’s ... by XtremeDevX on Saturday April 23, 2022 @09:56AM (#31134307)
This is exactly what we do, move the target/ directory on a ramdisk.