https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=0.11.0 2014-05-27T18:11:15+00:00 2014-05-27T18:11:15+00:00 Richo Healey richo@psych0tik.net 2014-05-25T10:10:11+00:00 urn:sha1:4348e23b269739657d934b532ad061bfd6d92309 2014-05-25T04:48:10+00:00 Richo Healey richo@psych0tik.net 2014-05-22T23:57:53+00:00 urn:sha1:553074506ecd139eb961fb91eb33ad9fd0183acb [breaking-change] 2014-05-17T08:01:47+00:00 Alex Crichton alex@alexcrichton.com 2014-05-16T21:23:04+00:00 urn:sha1:4e9e091e91ea2ad8a6f45a9b20ff331d4bca7a23 This is an implementation of RFC 16. A module can now only be loaded if the module declaring `mod name;` "owns" the current directory. A module is considered as owning its directory if it meets one of the following criteria: * It is the top-level crate file * It is a `mod.rs` file * It was loaded via `#[path]` * It was loaded via `include!` * The module was declared via an inline `mod foo { ... }` statement For example, this directory structure is now invalid // lib.rs mod foo; // foo.rs mod bar; // bar.rs; fn bar() {} With this change `foo.rs` must be renamed to `foo/mod.rs`, and `bar.rs` must be renamed to `foo/bar.rs`. This makes it clear that `bar` is a submodule of `foo`, and can only be accessed through `foo`. RFC: 0016-module-file-system-hierarchy Closes #14180 [breaking-change] 2014-05-14T21:58:00+00:00 Patrick Walton pcwalton@mimiga.net 2014-05-13T00:56:43+00:00 urn:sha1:95e310abdcbfe0f5ad511258097624719cbc84db 2014-04-19T00:25:34+00:00 Richo Healey richo@psych0tik.net 2014-04-16T01:17:48+00:00 urn:sha1:919889a1d688a6bbe2edac8705f048f06b1b455c 2013-07-04T17:51:11+00:00 Philipp Brüschweiler blei42@gmail.com 2013-07-04T17:51:11+00:00 urn:sha1:3c5cfdf2e7e53967eb330928aaeedfbb8ea1db4d Fixes #7276