-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Document unstable --extern
options
#98226
Conversation
Looks like highfive got confused - I'll go ahead and r? @ehuss |
This comment has been minimized.
This comment has been minimized.
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! Just a small addition. These really should have tracking issues, but I never got around to it.
I should probably squish all these commits if that's ok? |
Co-Authored-By: Joshua Nelson <github@jyn.dev> Co-Authored-By: Eric Huss <eric@huss.org>
Yeah, I think it would be nice to squash :) |
cbc3ce7
to
c20e0e1
Compare
Thanks! @bors r+ rollup |
📌 Commit c20e0e1 has been approved by |
Rollup of 10 pull requests Successful merges: - rust-lang#95446 (update CPU usage script) - rust-lang#96768 (Use futex based thread parker on Fuchsia.) - rust-lang#97454 (Add release notes for 1.62) - rust-lang#97516 (clarify how Rust atomics correspond to C++ atomics) - rust-lang#97818 (Point at return expression for RPIT-related error) - rust-lang#97895 (Simplify `likely!` and `unlikely!` macro) - rust-lang#98005 (Add some tests for impossible bounds) - rust-lang#98226 (Document unstable `--extern` options) - rust-lang#98356 (Add missing period) - rust-lang#98363 (remove use of &Alloc in btree tests) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
@ChrisDenton |
I could but I'd prefer to defer to @ehuss or someone else if they have the time. I don't really know the implementation details or history. But I can do a best effort attempt if it would help get the ball rolling. |
I'll set up the tracking issues later today. |
Posted #98401 to add links to the tracking issues. |
These are needed for Cargo's
build-std
feature and for anyone who wanted to do a similar thing outside of Cargo.