Weihang Lo
Weihang Lo
## Re: Backwards compatibility It sounds great to have a warning period. However, it's hard to give a "right" suggestion, as we don't know the intent of users even they...
Rebased due to the refactor of `cargo_compile/mod.rs`
Hi @ehuss. What is the status of this? Not urgent though 😉.
@zeroflaw Are you testing your project with this pull request? Could you provide a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) so that people can look into that? (Please open a new issue if...
> This is only true when calling OS APIs (and only if `longpathaware` isn't enabled). Paths can be stored and passed around as a user path then converted to a...
Possibly relevant discussions: * https://github.com/rust-lang/cargo/pull/7873 * https://github.com/rust-lang/cargo/issues/8140
Just [did a PoC] and benchmarks with rust-lang/cargo itself. It turns out that there is a slight performance hit (~5%) on macOS. It's in expectation, as there are some extra...
Cargo doesn't update dependencies at per-file-level. Cargo basically downloads new tarballs, unpacks them, and put files in separate directories.
@sanmai-NL could you elaborate more on how the approach resolves the concern in ? It may still fail people's builds, no?
Just jot it down: Tested method one and found that cargo 1.52 and later all got this issues.