pacak
pacak
esp with cargo-asm-show the usage string gets quote long, perhaps wrapping them heuristically at would be an option?
- [ ] - features - [ ] - `--profile` - [ ] - `--target-dir` - [ ] - don't insert separate `--package` when its already present
For example if crate depends on some other crate via a feature - hackerman might decide to turn optional dependency into mandatory, which is fine, but if `dep:used_to_be_optional_and_now_required` is present...
Fixes https://github.com/nix-rust/nix/issues/1954
At some point nixpkgs made a decision to include `cargo-auditable` wrapper of some sort which ends up passing attribute `auditable` to `rust-overlay`, failure looks like this: ``` error: function 'anonymous...
When running in a workspace with `parse-display 0.7.0` and `parse-display 0.8.0` available Running this ``` cargo upgrade -p parse-display ``` outputs this:  Excluded list contains a bit more info...
Clean build is a bit faster and a bit smaller ``` before: cargo build --release 70.39s user 3.50s system 823% cpu 8.976 total % ls -lha target/release/choose -rwxrwxr-x 2 pacak...
In particular what are those rough edges and which parts of the API are confusing? Comments I encounter on the Internet are mostly in favor of it as having small...
I noticed that the program I'm trying to monitor with dhat hangs when it is about to exit in some cases. Program prints stuff to stderr to report progress and...