-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Add error if link_ordinal used with unsupported link kind #100069
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @cjgillot (rust-highfive has picked a reviewer for you, use r? to override) |
r? @ehuss |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR, @dpaoliello!
I think the error message would be more helpful if it was
#[link_ordinal]
is only supported if link kind israw-dylib
that is, if raw-dylib
was mentioned explicitly.
Other than that, this looks good to go.
@bors r+ |
…iaskrgr Rollup of 8 pull requests Successful merges: - rust-lang#99573 (Stabilize backtrace) - rust-lang#100069 (Add error if link_ordinal used with unsupported link kind) - rust-lang#100086 (Add more `// unit-test`s to MIR opt tests) - rust-lang#100332 (Rename integer log* methods to ilog*) - rust-lang#100334 (Suggest a missing semicolon before an array) - rust-lang#100340 (Iterate generics_def_id_map in reverse order to fix P-critical issue) - rust-lang#100345 (docs: remove repetition in `is_numeric` function docs) - rust-lang#100352 (Update cargo) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
The
link_ordinal
attribute only has an affect if theraw-dylib
link kind is used, so add an error if it is used with any other link kind.