Add the keyword trusted for specifying "friend modules"#47
Conversation
There was a problem hiding this comment.
Moving the template shouldn't be part of the commit. You're supposed to copy it, edit your copy, and add the copy to the commit.
There was a problem hiding this comment.
I don't know how GitHub works. I simply tried to follow this guide to a T.
I can find a guide for creating a new file and moving a file, but not for copying a file at:
https://help.github.com/categories/81/articles
|
This was discussed in today's meeting: https://github.com/mozilla/rust/wiki/Meeting-weekly-2014-04-22#friend-modules---rfc-47 Friend modules have been considered before, and current consensus is that Rust provides enough tools for encapsulation that friend visibility is rarely needed. In particular, We may need to revisit friend visibility at some point in the future, but not now. I've closed this, assigned it RFC 10, but not accepted. Thank you for your time. |
|
Is it too soon to reconsider this? There are some useful things A possible alternative to Both solutions are backwards compatible, so not strictly necessary for 1.0. However I would argue that visibility trumping sense when it comes to module layout is an issue. It could certainly lead to awkwardly designed crate layouts, which in turn might be a BC problem after all. |
No description provided.