pacak

Results 102 issues of pacak

I have a workspace that contains git dependencies multiple times. cargo-outdated pulls each dependency every time it encounters one: ``` Updating git repository `https://github.com/Fuuzetsu/friedrich.git` Updating git repository `https://github.com/Fuuzetsu/rust-stats` Updating git...

``` #[bpaf(some)] pub ordercaches: Vec,``` this seems to generate .many() anyway: ``` let ordercaches = ::bpaf::long("ordercaches").help("The ordercaches used to drive the sim.").argument("ARG").from_str:: ().many();```

This generates named argument ```rust struct Options { #[bpaf(positional_os)] path: PathBuf, } ``` This works as expected: ```rust struct Options { #[bpaf(positional_os("PATH"))] path: PathBuf, } ```

https://docs.rs/bpaf_derive/0.1.3/bpaf_derive/ - postprocessing section, should probably link to corresponding bpaf help info

is there a way to not generate `pub` functions but just module-private ones? beyond wrapping everything in internal module and explicitly importing or something so that it warns if something...

drop the test, add an example describing the approach.

It is probably worth splitting docs into markdown for github and docs.rs parts. Currently CI fails on them.

Wrong: ``` [package.metadata.hackerman.stash.dependencies] smallvec = false ahash = false ``` Right: ``` [package.metadata.hackerman.stash.dependencies] ahash = false smallvec = false ```