-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Metadata failure with rust-socket crate #2170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
A-linkage
Area: linking into static, shared libraries and binaries
Comments
Things like this tend to happen when there are multiple matches for a single crate. Possibly try |
jdm's creader output:
|
I don't think this is a problem in crate resolution. @nikomatsakis suggests it could be related to monomorphising. |
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Sep 22, 2022
More robust comment parsing fixes rust-lang#2170 I haven't ported the entire test suite yet. Once we've done that, I will remove the old parsing system (or in fact, turn them into errors so that accidental usage of old-style comments will be detected)
Kobzol
pushed a commit
to Kobzol/rust
that referenced
this issue
Dec 30, 2024
Kobzol
pushed a commit
to Kobzol/rust
that referenced
this issue
Dec 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the following program:
using git head and the latest version of rust-socket (and a brand new build of rust-socket), the following build error occurs:
The text was updated successfully, but these errors were encountered: