Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@sunshowers
Copy link
Member

@sunshowers sunshowers commented Nov 28, 2023

Some dependencies don't have lib targets. While they can't be depended on in stable Rust, there's a nightly Rust feature that enables use of binary-only dependencies. In those cases, the resolved_name is an empty string.

Also added mnemos to our corpus.

Some dependencies don't have lib targets. While they can't be depended on in
stable Rust, there's a nightly Rust feature that enables use of binary-only
dependencies. In those cases, the `resolved_name` is an empty string.
@sunshowers
Copy link
Member Author

sunshowers commented Nov 29, 2023

Note that this isn't a complete fix -- currently we don't have enough information to achieve that. I added this info in a subsequent commit d1e9736

                // This code path is only hit with nightly Rust as of 2023-11. It depends on Rust
                // RFC 3028. at https://github.com/rust-lang/cargo/issues/9096.
                //
                // This isn't quite right -- if we have two or more non-lib dependencies, we'll
                // return true for both of them over here. What we need to do instead is use the
                // extern_name and bin_name fields that are present in nightly DepKindInfo, but that
                // aren't in stable yet. For now, this is the best we can do.
                //
                // (If we're going to be relying on heuristics, it is also possible to use the
                // package ID over here, but that's documented to be an opaque string. It also
                // wouldn't be resilient to patch and replace.)

sunshowers added a commit to nextest-rs/nextest that referenced this pull request Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant