Weihang Lo

Thank your for providing a solution on this topic! Most of your understanding is correct. Each test target, either unit test or integration test results in a linker invocation. You...

I'd say it looks like a bug since its first introduction[^0]. The original intent was skipping dot directories but seems to accidentally do that on dotfiles as well. Most of...

That's because fingerprint take source file paths into account [^1]. Currently, fingerprint calculation mostly relies on filesystem mtime and paths, not content hashes. Cargo never know the intent of a...

> What if we instead hashed relative to CARGO_HOME? Personally I am happy towards this. My little concern is that someone already relies on switching `CARGO_HOME` for different registry index...

There are some complications about caching artifacts and metadata when changing paths in Cargo. Here is [one thread](https://github.com/rust-lang/cargo/issues/9887) discussing such issue. You could check this rustc flag [`--remap-path-prefix`] to see...

This is really an interesting proposal! I believe this kind of display format is achievable with tweaks in the current ad-hoc implementation. However, Cargo team is working on improving the...

It seems good if we can ship this doc enhancement in 1.64. Should we send a PR to beta as well?

Thank you! @bors r+

From my understanding, [the change you referred to][change] might not be the root cause. Either [config-include] or [`Config::_load_file`] will eventually create a `ConfigValue` with `Definition::Path`. As `Definition::Path` is [the lowest...

FWIW, there is an ongoing project on integrating gitoxide[^1] to replace some uses of libgit2 in Cargo. I wouldn't say it will be landed soon but we can keep a...