Weihang Lo

Another way to manage this is to have all dependencies specified under `workspace.dependencies` with `default-features = false`, so we'll have a (slightly) better view when a feature is really needed.

Could also consider committing a MSRV compatible `Cargo.lock`, so it becomes a source of true of what is buildable. And Optionally have a non-blocking "latest version" job for verification purpose....

> Adding a "dirty" field would help here, unless they are just looking for the file (not the contents of the file. In which case there really isn't much you...

is also related I believe.

> With the current default, if a user wants to find a conflicting package, it can be detected as an error. Automatic collision avoidance will not find conflicting packages. In...

Thanks for being enthusiastic about this! --- > > `{ patches = [] }` field is only available for dependencies under `[patch]` table, > > and only allows patching registry...

@NeuralModder thanks for your sharing. > (I'm also wondering now if this is a bug in dependency resolution that could actually just be fixed...) I think that is possibly a...

Just FYI, it will be available in next one or two nightly release .

Sorry for the late response. This is an interesting case! Let me tell what happen. In jemalloc, they have [a `.gitignore` rule](https://github.com/jemalloc/jemalloc/blob/5afff2e44e8d31ef1e9eb01d6b1327fe111835ed/.gitignore#L67-L68) excluding everything under `/test/stress/[A-Za-z]*`. I believe this will...

Thanks for the report! And really sorry for the late response. Haven't got more time looking into this, but found more inconsistencies: ``` vendor --manifest-path wardstone/Cargo.toml --sync rkv/Cargo.toml # ❌...