Rolling up PRs in the queue #17343
Merged
Rolling up PRs in the queue #17343
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The lint checks any unnecessary braces around one imported item like
`use std::num::{abs};`.
Signed-off-by: OGINO Masanori <[email protected]>
Without 'notrust,' we were getting a playpen link. Fixes rust-lang#17228.
Adds a new configure flag, --release-channel, which determines how the version number should be augmented with a release label, as well as how the distribution artifacts will be named. This is entirely for use by the build automation. --release-channel can be either 'source', 'nightly', 'beta', or 'stable'. Here's a summary of the affect of these values on version number and artifact naming, respectively: * source - '0.12.0-pre', 'rust-0.12.0-pre-...' * nightly - '0.12.0-nightly', 'rust-nightly-...' * beta - '0.12.0-beta', 'rust-beta-...' * stable - '0.12.0', 'rust-0.12.0-...' Per http://discuss.rust-lang.org/t/rfc-impending-changes-to-the-release-process/508/1
1000 tasks * 2MiB stack size -> 2GiB of virtual memory On a 64-bit OS, a 32-bit executable has 4GiB available, but the kernel gets half of the available address space so the limit is 2GiB on 32-bit. Closes rust-lang#17044
This closes rust-lang#17260. The guide references the old install location for the windows rust install before it was split into 64bit and 32bit installers. This adds a link to each binary.
Renamed as we may support pipes for other platforms. Closes rust-lang#12093 [breaking-change]
lifetime bounds. This doesn't really cause any difficulties, because we already had to accommodate the fact that multiple implicit bounds could accumulate. Object types still require precisely one lifetime bound. This is a pre-step towards generalized where clauses (once you have lifetime bounds in where clauses, it is harder to restrict them to exactly one).
This is part of the migration of crates into the Cargo ecosystem. There is now an external repository https://github.com/rust-lang/num for bignums. The single use of libnum elsewhere in the repository is for a shootout benchmark, which is being moved into the external crate. Due to deprecation, this is a: [breaking-change]
HOME does not exist under typical windows environments.
This is the first linux snapshot created on our new CentOS 5.10 builders. Closes rust-lang#9545
This makes having multiple restrictions at once cleaner. Also drop NO_DOUBLEBAR restriction since it is never used.
This prevents confusing errors when accidentally using an assignment
in an `if` expression. For example:
```rust
fn main() {
let x = 1u;
if x = x {
println!("{}", x);
}
}
```
Previously, this yielded:
```
test.rs:4:16: 4:17 error: expected `:`, found `!`
test.rs:4 println!("{}", x);
^
```
With this change, it now yields:
```
test.rs:3:8: 3:13 error: mismatched types: expected `bool`, found `()` (expected bool, found ())
test.rs:3 if x = x {
^~~~~
```
Closes issue rust-lang#17283
Avoids warnings during bootstrap, similar to: src/librustc/lib.rs:149:1: 149:39 warning: diagnostic code E0099 never used src/librustc/lib.rs:149 __build_diagnostic_array!(DIAGNOSTICS) All of these codes stopped being used in this commit: 688ddf7 ("typeck/kind -- stop using old trait framework.") See also similar fix: rust-lang#16449
This is done by adding a new field to the `DefTy` variant of `middle::def::Def`, which also clarifies an error message in the process. Closes rust-lang#16712.
…-to-multiple-object-bounds
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.