Josh Triplett

Make the `rust-version` error recommend `cargo update --precise -p crate@ver`

3

People encountering a dependency with a newer `rust-version` requirement may not know about `cargo update --precise`, or may consider alternate approaches that may be harmful (such as pinning with a...

Should integrate cc-rs knowledge of linkers with rustc

2

rustc currently has limited knowledge of the correct linker to use on various platforms. cc-rs has a much better idea of which linker to use. There's been a long-standing goal...

Support compiling different files with different options

4

I'd like to have better support for compiling different files with different compiler options. For instance, I'd like to compile `avx2-foo.c` with `-mavx2`, without applying that flag to any other...

Reading files from within const eval

7

(Filing this at @oli-obk's request, based on discussions on Zulip.) We should be able to read files within const eval. This is equivalent to doing `include_bytes!` (which we already support...

Listing directories or matching globs in const evaluation

1

(Filing this at @oli-obk's request, based on discussions on Zulip. Related to https://github.com/rust-lang/const-eval/issues/44 .) We should be able to get lists of files on the filesystem, within const eval. This...

Sometimes, it would suffice to see if a code pattern exists, without having to actually run the compiler in check mode. That would be much faster, and would often provide...

Please support running standalone

4

cargo-tree expects to find a local Cargo.toml file. Please consider adding support for running on a named package directly from the registry: `cargo tree somecrate`.

Please support enabling zstd long-distance matching mode

3

async-compression only allows passing a numeric level. I'd love to enable the zstd "long-distance matching mode", which substantially improves compression on large files that may have similarity at long distances....

This allows enabling parameters such as long-distance matching mode or rsyncable mode.

Consider `#[track_caller]` on functions that panic

2

For functions that panic, such as `extend`, please consider using `#[track_caller]`, to provide more meaningful location information for debugging such panics. (This report inspired by debugging an ArrayVec panic inside...