You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A mechanism for std to be a "friend" of core would solve both of these without making libcore grow tremendously large. I'm not sure how crate metadata works, but I could imagine writing export mod in a crate file would export the module publically, while all other modules do get exported, only privately.
The text was updated successfully, but these errors were encountered:
add aarch64-apple-darwin to list of supported targets
I did not realize that aarch64-apple-darwin is a tier 2 target. We are testing it properly, even on rustc CI, so we might as well list it as fully supported here.
celinval
added a commit
to celinval/rust-dev
that referenced
this issue
Jun 4, 2024
There are already several things either (a) in libcore that should be in libstd or (b) inappropriately exported from libcore.
A mechanism for std to be a "friend" of core would solve both of these without making libcore grow tremendously large. I'm not sure how crate metadata works, but I could imagine writing
export mod
in a crate file would export the module publically, while all other modules do get exported, only privately.The text was updated successfully, but these errors were encountered: