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.
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 modin a crate file would export the module publically, while all other modules do get exported, only privately.