mirror of
https://github.com/cargo-bins/cargo-binstall.git
synced 2025-04-20 12:38:43 +00:00
c5d0b84aa6
The startup/init code in `entry::install_crates` performs a lot of blocking operations, from testing if dir exists to reading from files and there is no `.await` in there until after the startup. There are also a few cases where `block_in_place` should be called (e.g. loading manifests, loading TLS certificates) but is missing. Most of the `Args` passed to `entry::install_crates` are actually consumed before the first `.await` point, so performing startup/init code eagerly would make the generated future much smaller, reduce codegen and also makes it easier to optimize. Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com> |
||
|---|---|---|
| .. | ||
| bin | ||
| binstalk | ||
| binstalk-downloader | ||
| binstalk-manifests | ||
| binstalk-types | ||
| detect-targets | ||
| detect-wasi | ||
| fs-lock | ||
| normalize-path | ||