- 01 3月, 2015 1 次提交
-
-
由 Björn Steinbrink 提交于
Fixes #20467
-
- 28 2月, 2015 17 次提交
-
-
由 bors 提交于
This pulls out the implementations of most built-in lints into a separate crate, to reduce edit-compile-test iteration times with librustc_lint and increase parallelism. This should enable lints to be refactored, added and deleted much more easily as it slashes the edit-compile cycle to get a minimal working compiler to test with (`make rustc-stage1`) from librustc -> librustc_typeck -> ... -> librustc_driver -> libcore -> ... -> libstd to librustc_lint -> librustc_driver -> libcore -> ... libstd which is significantly faster, mainly due to avoiding the librustc build itself. The intention would be to move as much as possible of the infrastructure into the crate too, but the plumbing is deeply intertwined with librustc itself at the moment. Also, there are lints for which diagnostics are registered directly in the compiler code, not in their own crate traversal, and their definitions have to remain in librustc. This is a [breaking-change] for direct users of the compiler APIs: callers of `rustc::session::build_session` or `rustc::session::build_session_` need to manually call `rustc_lint::register_builtins` on their return value. This should make #22206 easier.
-
由 Huon Wilson 提交于
-
由 Huon Wilson 提交于
This pulls out the implementations of most built-in lints into a separate crate, to reduce edit-compile-test iteration times with librustc_lint and increase parallelism. This should enable lints to be refactored, added and deleted much more easily as it slashes the edit-compile cycle to get a minimal working compiler to test with (`make rustc-stage1`) from librustc -> librustc_typeck -> ... -> librustc_driver -> libcore -> ... -> libstd to librustc_lint -> librustc_driver -> libcore -> ... libstd which is significantly faster, mainly due to avoiding the librustc build itself. The intention would be to move as much as possible of the infrastructure into the crate too, but the plumbing is deeply intertwined with librustc itself at the moment. Also, there are lints for which diagnostics are registered directly in the compiler code, not in their own crate traversal, and their definitions have to remain in librustc. This is a [breaking-change] for direct users of the compiler APIs: callers of `rustc::session::build_session` or `rustc::session::build_session_` need to manually call `rustc_lint::register_builtins` on their return value. This should make #22206 easier.
-
由 bors 提交于
This adds the assume() calls back that got lost when rebasing #21886.
-
由 bors 提交于
Passes check-stage1, check-stage2
-
由 Alex Crichton 提交于
-
由 Manish Goregaokar 提交于
Refactor signaling of E0223 to avoid multiple span_errs for same code. (Doing this cuts out one diagnostic during the build.)
-
由 Felix S. Klock II 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
Closes #21721.
-
由 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 19 次提交
-
-
由 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 提交于
-
由 Tshepang Lekhonkhobe 提交于
-
由 Dave Huseby 提交于
-
由 Valerii Hiora 提交于
-
- 26 2月, 2015 3 次提交
-
-
由 bors 提交于
In the process, also replaces two raw mutable pointers with `Unique` to spell out the ownership semantics. cc #22709
-
由 Seo Sanghyeon 提交于
-
由 Seo Sanghyeon 提交于
-