- 13 1月, 2017 1 次提交
-
-
由 Esteban Küber 提交于
For a given file ```rust trait A { fn foo(&self) {} } trait B : A { fn foo(&self) {} } fn bar<T: B>(a: &T) { a.foo() } ``` provide the following output ``` error[E0034]: multiple applicable items in scope --> file.rs:6:5 | 6 | a.foo(1) | ^^^ multiple `foo` found | note: candidate #1 is defined in the trait `A` --> file.rs:2:11 | 2 | trait A { fn foo(&self, a: usize) {} } | ^^^^^^^^^^^^^^^^^^^^^^^^^^ help: to use it here write `A::foo(&a, 1)` instead --> file.rs:6:5 | 6 | a.foo(1) | ^^^ note: candidate #2 is defined in the trait `B` --> file.rs:3:15 | 3 | trait B : A { fn foo(&self, a: usize) {} } | ^^^^^^^^^^^^^^^^^^^^^^^^^^ help: to use it here write `B::foo(&a, 1)` instead --> file.rs:6:5 | 6 | a.foo(1) | ^^^ ```
-
- 14 6月, 2016 1 次提交
-
-
由 Chris Tomlinson 提交于
-
- 13 6月, 2016 1 次提交
-
-
由 Chris Tomlinson 提交于
-
- 07 5月, 2016 2 次提交
-
-
由 Niko Matsakis 提交于
For legacy reasons (presumably), Windows does not permit files name aux.
-
由 Niko Matsakis 提交于
Instead of finding aux-build files in `auxiliary`, we now search for an `aux` directory relative to the test. So if your test is `compile-fail/foo.rs`, we would look in `compile-fail/aux`. Similarly, we ignore the `aux` directory when searching for tets.
-
- 11 2月, 2016 1 次提交
-
-
由 Björn Steinbrink 提交于
LLVM's memory dependence analysis doesn't properly account for calls that could unwind and thus effectively act as a branching point. This can lead to stores that are only visible when the call unwinds being removed, possibly leading to calls to drop() functions with b0rked memory contents. As there is no fix for this in LLVM yet and we want to keep compatibility to current LLVM versions anyways, we have to workaround this bug by omitting the noalias attribute on &mut function arguments. Benchmarks suggest that the performance loss by this change is very small. Thanks to @RalfJung for pushing me towards not removing too many noalias annotations and @alexcrichton for helping out with the test for this bug. Fixes #29485
-
- 09 1月, 2016 1 次提交
-
-
由 Niko Matsakis 提交于
Fixes #29857. Fixes #30589.
-
- 08 1月, 2016 1 次提交
-
-
由 Felix S. Klock II 提交于
macro future proofing rules. (We may want to think about what this test was actually testing and figure out a way to test it without running afoul of macro future proofing. I spent some time trying to do this, e.g. by inserting parenthesis in the macro input pattern, but I could not quickly get it working, so I took this tack instead.)
-
- 06 1月, 2016 1 次提交
-
-
由 Nick Cameron 提交于
Fixes #30715
-
- 24 3月, 2015 1 次提交
-
-
由 Brian Anderson 提交于
Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work.
-
- 17 11月, 2014 1 次提交
-
-
由 Steven Fackler 提交于
This breaks code that referred to variant names in the same namespace as their enum. Reexport the variants in the old location or alter code to refer to the new locations: ``` pub enum Foo { A, B } fn main() { let a = A; } ``` => ``` pub use self::Foo::{A, B}; pub enum Foo { A, B } fn main() { let a = A; } ``` or ``` pub enum Foo { A, B } fn main() { let a = Foo::A; } ``` [breaking-change]
-
- 24 4月, 2014 1 次提交
-
-
由 Steven Fackler 提交于
RFC: 0008-match-arm-attributes
-
- 08 2月, 2014 1 次提交
-
-
由 Derek Guenther 提交于
-
- 25 9月, 2013 1 次提交
-
-
由 Alex Crichton 提交于
This is required by the check-fast target because each test is slurped up into a submodule.
-
- 14 6月, 2013 1 次提交
-
-
由 Daniel Micay 提交于
-
- 31 5月, 2013 1 次提交
-
-
由 Patrick Walton 提交于
-