You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nice to have process trees on Windows ; GUIs like Process Explorer or TMX are fine but they can't be used in scripts/tools.
I hit a minor issue : 0.1.1 builds and runs fine but only with +nightly:
$ cargo install proctree
.
.
.
Compiling proctree v0.1.1
error[E0554]: `#![feature]` may not be used on the stable release channel
--> C:\Users\olivier\.cargo\registry\src\github.com-1ecc6299db9ec823\proctree-0.1.1\src\main.rs:1:12
|
1 | #![feature(drain_filter)]
| ^^^^^^^^^^^^
Unfortunately, the drain_filter function is still nightly only and requires the feature gate #![feature(drain_filter)] it might make sense to account for this in the installation instructions or change to a different approach until the API has been stabilized.
Yes sorry for having been unclear about "minor" issue : I meant that's only a doc issue, not an actual bug.
Though I greatly value the FP way, maybe a simple while + remove loop as in drain_filter will fit until this feature is stabilized (though it will perform worse).
Rust is gaining a lot of traction, and newcomers may not know about nightly toolchain.
Since I moved away from nodejs to tokio for my backend code I can't stand 'npm install' problems anymore, and I give myself duty to report anything that makes the rust experience sub-optimal, morevorer about tools I 'cargo install'.
Nice to have process trees on Windows ; GUIs like Process Explorer or TMX are fine but they can't be used in scripts/tools.
I hit a minor issue : 0.1.1 builds and runs fine but only with +nightly:
Platform : Windows 10
Nightly :
Runs fine
Good job !
The text was updated successfully, but these errors were encountered: