- 08 3月, 2016 1 次提交
-
-
由 Ulrik Sverdrup 提交于
- Mention the sugared syntax for the implementations, since it's not apparent from the docs that `Index<Range<usize>>` corresponds to `&self[a..b]`. - Be specific in that start <= end and end <= len
-
- 04 3月, 2016 12 次提交
-
-
由 bors 提交于
- Empty `.sidebar .location` caused "grey line" on top of the documentation page (under 700px) fixed. - `.sidebar .location` appearance improvement in responsive mode.
-
由 bors 提交于
This PR changes the search paths for macro-expanded non-inline modules so that they match ordinary non-inline modules (fixes #31624). This is a [breaking-change]. Right now, the search paths for a macro-expanded non-inline module are computed as if the module were declared in the top level of the file in which the macro was defined. For example, consider `./foo/mod.rs`: ```rust mod inconsequential { // moving the macro outside this module wouldn't change anything macro_rules! mod_decl { ($i:ident) => { mod $i; } } } ``` and `./lib.rs`: ```rust mod foo; mod bar { mod_decl!(baz); //^ Now, rustc expects `./foo/baz.rs` (or `./foo/baz/mod.rs`) //| After this PR, rustc will expect `./bar/baz.rs` (or `./bar/baz/mod.rs`) } ``` r? @alexcrichton
-
由 bors 提交于
I have these tagged as stable in 1.9, so this shouldn't merge until the 1.8 beta's cut.
-
由 Ariel Ben-Yehuda 提交于
Fixes #30891
-
由 bors 提交于
Show `cfg` as possible argument to `--print` and make it so that `--print cfg` also outputs the `target_feature`s. Should I also extend `src/test/run-make/print-cfg/Makefile` to check that `target_feature`s are actually printed?
-
由 Steven Fackler 提交于
-
由 bors 提交于
This PR extends compiletest to support **test revisions** and with a preliminary **incremental testing harness**. run-pass, compile-fail, and run-fail tests may be tagged with ``` // revisions: a b c d ``` This will cause the test to be re-run four times with `--cfg {a,b,c,d}` in turn. This means you can write very closely related things using `cfg`. You can also configure the headers/expected-errors by writing `//[foo] header: value` or `//[foo]~ ERROR bar`, where `foo` is the name of your revision. See the changes to `coherence-cow.rs` as a proof of concept. The main point of this work is to support the incremental testing harness. This PR contains an initial, unused version. The code that uses it will land later. The incremental testing harness compiles each revision in turn, and requires that the revisions have particular names (e.g., `rpass2`, `cfail3`), which tell it whether a particular revision is expected to compile or not. Two questions: - Is there compiletest documentation anywhere I can update? - Should I hold off on landing the incremental testing harness until I have the code to exercise it? (That will come in a separate PR, still fixing a few details) r? @alexcrichton cc @rust-lang/compiler <-- new testing capabilities
-
由 Steven Fackler 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
should-fail annotation
- 03 3月, 2016 24 次提交
-
-
由 Niko Matsakis 提交于
-
由 Andrea Canciani 提交于
Gated cfg attributes are not available on the stable and beta release channels, therefore they should not be presented to users of those channels in order to avoid confusion.
-
由 bors 提交于
Use `drop_in_place` in Vec and VecDeque We can use drop_in_place's DST capabilities directly in Vec::drop and similarly in VecDeque::drop. I verfied this has the same effect as the previous `needs_drop` code; `drop_in_place` it itself an intrinsic. The VecDeque replacement should be more efficient too, even in release mode (slice iteration makes a more efficient loop than the deque iterator).
-
由 Jeffrey Seyfried 提交于
-
由 Steven Fackler 提交于
-
由 gohyda 提交于
-
由 bors 提交于
This PR privacy checks paths as they are resolved instead of in `librustc_privacy` (fixes #12334 and fixes #31779). This removes the need for the `LastPrivate` system introduced in PR #9735, the limitations of which cause #31779. This PR also reports privacy violations in paths to intra- and inter-crate items the same way -- it always reports the first inaccessible segment of the path. Since it fixes #31779, this is a [breaking-change]. For example, the following code would break: ```rust mod foo { pub use foo::bar::S; mod bar { // `bar` should be private to `foo` pub struct S; } } impl foo::S { fn f() {} } fn main() { foo::bar::S::f(); // This is now a privacy error } ``` r? @alexcrichton
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
由 Jeffrey Seyfried 提交于
-
由 bors 提交于
Fix note for type alias in trait position Fixes #31686
-
由 Andrea Canciani 提交于
The configuration returned by `config::build_configuration` needs to be modified with `target_features::add_configuration` in order to also contain the target features. This is already done for the configuration used when compiling and when creating the documentation, but was missing in the `cfg` printing code.
-
由 Andrea Canciani 提交于
The `--print` flag was extended in #31278 to accept `cfg`, but the usage message was not updated.
-
由 vegai 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
and write a really basic "meta test" of the compilertest framework
-
由 Niko Matsakis 提交于
-
由 bors 提交于
This fixes the `x86_64-rumprun-netbsd` target. r? @alexcrichton
-
由 vegai 提交于
-
由 Ulrik Sverdrup 提交于
Just like for Vec. This should benefit both non-optimized and optimized performance. Non-optimized since the intrinsic drop_in_place is easily removed, and optimized because iterating the slices is more efficient than using the VecDeque iterators.
-
由 Ulrik Sverdrup 提交于
-
由 Ulrik Sverdrup 提交于
Directly use the drop glue for [T]. Still optimizes out in -O1 like with the `needs_drop` intrinsic.
- 02 3月, 2016 3 次提交
-
-
由 bors 提交于
Vectors come up in sections dedicated to ownership with the assumption that we know something about it but we haven't seen it yet. On the other hand, you need not know anything about ownership or lifetimes to understand the basics of vectors covered in the vector section of the book. Additionally, by moving it where it is there is a natural progression from loops to an iterative type which discusses for loops. This kind of interaction is generally better for learning. I would like to have moved the struct section as well but I'm less confident about how to handle it since the ownership sections discuss structs and the structs section talks about mutable borrow.
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-