diff options
| author | bors <bors@rust-lang.org> | 2013-05-06 18:57:40 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-05-06 18:57:40 -0700 |
| commit | 4b6864f2195250d34cbedf92ffaf23a400c71b9e (patch) | |
| tree | ed2b88be974c41bb1ec6d8f6e69bcd4a7f803d54 /src/libsyntax/parse/parser.rs | |
| parent | 05460fcd5a9b2be5055f55965f768b0aa37119d9 (diff) | |
| parent | 24cda9fbc20cad2d7f59a40973a51ff6355ababb (diff) | |
| download | rust-4b6864f2195250d34cbedf92ffaf23a400c71b9e.tar.gz rust-4b6864f2195250d34cbedf92ffaf23a400c71b9e.zip | |
auto merge of #6226 : alexcrichton/rust/issue-6199, r=brson
I just removed `pub mod` from `core.rc` and then got everything to compile again. One thing I'm worried about is an import like this:
```rust
use a;
use a::b;
mod a {
pub type b = int;
}
mod b {
use a; // bad
use a::b; // good
}
```
I'm not sure if `use a::b` being valid is a bug or intended behavior (same question about `use a`). If it's intended behavior, then I got around these modules not being public by only importing the specific members that are necessary. Otherwise that probably needs an open issue.
Diffstat (limited to 'src/libsyntax/parse/parser.rs')
0 files changed, 0 insertions, 0 deletions
