- 28 2月, 2015 7 次提交
-
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
The branch \"else { continue }\" is the last code inside a loop body, it is just useless. Signed-off-by: NLai Jiangshan <laijs@cn.fujitsu.com>
-
由 Manish Goregaokar 提交于
Changes .or() so that it can return a Result with a different E type than the one it is called on. Essentially: fn or(self, res: Result<T, E>) -> Result<T, E> becomes fn or<F>(self, res: Result<T, F>) -> Result<T, F> This brings `or` in line with the existing `and` & `or_else` This is a [breaking-change] Due to some code needing additional type annotations.
-
由 Manish Goregaokar 提交于
Change MarkerTrait to be invariant. This is a (small) loss of expressiveness, but is necessary for now to work around #22806. Fixes #22655. r? @pnkfelix
-
由 Manish Goregaokar 提交于
Keeps the method consistent with `Iterator::any`. Closes #22617 [breaking-change]
-
由 Manish Goregaokar 提交于
which starts happening after ~2 hours of machine uptime. Closes #17845
- 27 2月, 2015 18 次提交
-
-
由 Manish Goregaokar 提交于
r? @steveklabnik Closes #22698 I wasn't sure that this was appropriate for the book, but I've added this to the reference. I also noticed that one of the U+ symbols in the character literals section was missing the graves.
-
由 Manish Goregaokar 提交于
r? @steveklabnik
-
由 Manish Goregaokar 提交于
This patch contains a couple time fixes to make Rust compile on Bitrig again. This does not affect OpenBSD.
-
由 Manish Goregaokar 提交于
"body": null,
-
由 Manish Goregaokar 提交于
Fixes #21370. `unused-macro-with-follow-violation.rs` was already handled correctly. That test is just for good measure. :) I have a more involved plan to clean this up, but it ran into difficulties such as #22814.
-
由 Manish Goregaokar 提交于
Ensure we do not zero when \"moving\" types that are Copy. Uses more precise `type_needs_drop` for deciding about emitting cleanup code. Added notes about the weaknesses regarding `ty::type_contents` here. Fix #22536
-
由 Manish Goregaokar 提交于
We were recording stability attributes applied to fields in the compiler, and even annotating it in the libs, but the compiler didn't actually do the checks to give errors/warnings in user crates. Details in the commit messages.
-
由 bors 提交于
Implements `Debug` for `RwLock` and `arc::Weak` in the same way it is implemented for `rc::Weak` (basically copy & paste). The lack of this implementation prevents the automatic implementation of `Debug` for structs containing members of these types.
-
由 bors 提交于
r? @alexcrichton cc @nikomatsakis @pnkfelix
-
由 bors 提交于
Instead of allocating the same ports for ipv4 and ipv6 tests, instead draw all ports from the same pool. Some tests connect to just "localhost" on a particular port which may accidentally be interacting with other tests as the ipv-what-ness isn't specified with the string "localhost" Relevant logs: * [Deadlock of the `net::tcp::tests::listen_localhost` test][mac] * [Failure of the `fast_rebind` test][win1] * [Failure of `multiple_connect_interleaved_lazy_schedule_ip4`][win2] [mac]: https://gist.github.com/alexcrichton/349c7ce7c620c1adb2f2 [win1]: https://gist.github.com/alexcrichton/7e3611faae2e1edaee6f [win2]: https://gist.github.com/alexcrichton/4f5f87749af3ad0f9851
-
由 Alex Crichton 提交于
Instead of allocating the same ports for ipv4 and ipv6 tests, instead draw all ports from the same pool. Some tests connect to just "localhost" on a particular port which may accidentally be interacting with other tests as the ipv-what-ness isn't specified with the string "localhost" Relevant logs: * [Deadlock of the `net::tcp::tests::listen_localhost` test][mac] * [Failure of the `fast_rebind` test][win1] * [Failure of `multiple_connect_interleaved_lazy_schedule_ip4`][win2] [mac]: https://gist.github.com/alexcrichton/349c7ce7c620c1adb2f2 [win1]: https://gist.github.com/alexcrichton/7e3611faae2e1edaee6f [win2]: https://gist.github.com/alexcrichton/4f5f87749af3ad0f9851
-
由 bors 提交于
rustdoc impl item did not include default methods for local crates, but did include them for external crates. This resulted in duplicate methods. Fix so that impl item does not include default methods for external crates. Fix #22595.
-
由 Huon Wilson 提交于
-
由 Julian Orth 提交于
Useful for debugging tests that hang forever.
-
由 Flavio Percoco 提交于
-
由 Dave Huseby 提交于
-
由 Valerii Hiora 提交于
-
- 26 2月, 2015 15 次提交
-
-
由 bors 提交于
In the process, also replaces two raw mutable pointers with `Unique` to spell out the ownership semantics. cc #22709
-
由 Seo Sanghyeon 提交于
-
由 Seo Sanghyeon 提交于
-
由 Felix S. Klock II 提交于
-
由 Felix S. Klock II 提交于
-
由 Felix S. Klock II 提交于
Fix #22536
-
由 Felix S. Klock II 提交于
(Instrumentation work for Issue 22536.)
-
由 Lai Jiangshan 提交于
The branch "else { continue }" is the last code inside a loop body, it is just useless. Signed-off-by: NLai Jiangshan <laijs@cn.fujitsu.com>
-
由 bors 提交于
This needs to make it into the snapshot before #21824 can land. r? @alexcrichton
-
由 nwin 提交于
-
由 Edward Wang 提交于
In the process, also replaces a raw mutable pointers with Unique to spell out the ownership semantics. cc #22709
-
由 bors 提交于
The Path/PathBuf pair already implements the required `Borrow`/`ToOwned` traits and can be used in a `Cow` pointer, so why not? r? @alexcrichton
-
由 Steven Fackler 提交于
-
由 Edward Wang 提交于
So it is symmetric to its `Iter` implementation. Also kills an FIXME.
-
由 Huon Wilson 提交于
The stability check checks the `PublicItems` map when giving errors if there is a #[stable] item with a public contents that doesn't not have its own stability. Without recording this, struct fields and enum variants will not get errors for e.g. stable modules with unmarked functions internally. This is just improving the compiler's precision to give the standard library developers more information earlier. E.g. #![staged_api] #![feature(staged_api)] #![crate_type = "lib"] #[stable(feature = "rust1", since = "1.0.0")] pub struct Foo { pub x: i32 } #[stable(feature = "rust1", since = "1.0.0")] pub mod bar { pub fn baz() {} } Without the patch it gives: test.rs:12:5: 12:20 error: This node does not have a stability attribute test.rs:12 pub fn baz() {} ^~~~~~~~~~~~~~~ error: aborting due to previous error With the patch it gives: test.rs:7:9: 7:15 error: This node does not have a stability attribute test.rs:7 pub x: i32 ^~~~~~ test.rs:12:5: 12:20 error: This node does not have a stability attribute test.rs:12 pub fn baz() {} ^~~~~~~~~~~~~~~ error: aborting due to 2 previous errors
-