- 25 6月, 2014 2 次提交
-
-
由 Keegan McAllister 提交于
-
由 Keegan McAllister 提交于
We're going to have more modules under lint, and the paths get unwieldy. We also plan to have lints run at multiple points in the compilation pipeline.
-
- 24 6月, 2014 18 次提交
-
-
由 bors 提交于
Fix #15052
-
由 bors 提交于
The aim of these changes is not working out a generic bi-endianness architectures support but to allow people develop for little endian MIPS machines (issue #7190).
-
由 Tom Jakubowski 提交于
Fix #15052
-
由 bors 提交于
Includes a bit more comments than usual for a regression test; I felt like documenting Niko's diagnosis of the original problem here. Fix #15111 r? anyone.
-
由 bors 提交于
-
由 Pawel Olzacki 提交于
-
由 bors 提交于
If you define lang items in your crate, add `#[feature(lang_items)]`. If you define intrinsics (`extern "rust-intrinsic"`), add `#[feature(intrinsics)]`. Closes #12858. [breaking-change] r? @brson
-
由 Patrick Walton 提交于
If you define lang items in your crate, add `#[feature(lang_items)]`. If you define intrinsics (`extern "rust-intrinsic"`), add `#[feature(intrinsics)]`. Closes #12858. [breaking-change]
-
由 bors 提交于
This is just a cleanup of the code. Doesn't really change anything deep about the way we operate. This is a prelude to implementing a good solution for one-way matching for #5527. r? @pnkfelix (we were just crawling about this code, after all)
-
由 bors 提交于
This does not yet change the compiler and libraries from `*T` to `*const T` as it will require a snapshot to do so. cc #7362 --- Note that the corresponding RFC, https://github.com/rust-lang/rfcs/pull/68, has not yet been accepted. It was [discussed at the last meeting](https://github.com/rust-lang/rust/wiki/Meeting-weekly-2014-06-10#rfc-pr-68-unsafe-pointers-rename-t-to-const-t) and decided to be accepted, however. I figured I'd get started on the preliminary work for the RFC that will be required regardless.
-
由 bors 提交于
-
由 bors 提交于
`for...in`. Closes #14803. If you used a structure literal after one of these keywords, surround it in parentheses. [breaking-change] r? @nick29581
-
由 Patrick Walton 提交于
`for...in`. Closes #14803. If you used a structure literal after one of these keywords, surround it in parentheses. [breaking-change]
-
由 Ivan Petkov 提交于
-
由 bors 提交于
Closes #3973.
-
由 Kevin Butler 提交于
-
由 Kevin Butler 提交于
Closes #3973.
-
由 bors 提交于
Even if they used to test different things in the past, they are now identical to other files. Closes #11496
-
- 23 6月, 2014 15 次提交
-
-
由 bors 提交于
/usr/bin/env appears to be more portable.
-
由 bors 提交于
Reject `struct Foo();` to fix #15095.
-
由 Felix S. Klock II 提交于
-
由 bors 提交于
fix #12291
-
由 bors 提交于
Turns out field names of struct variants are not encoded in crate metadata.
-
由 bors 提交于
Closes #15031.
-
由 bors 提交于
In other words, Late-bound regions that occur non-free should be skipped. Fix #10846 (specifically the ICE, not the weakness in the current type inference).
-
由 Alex Crichton 提交于
-
由 bors 提交于
See http://static.rust-lang.org/doc/master/rustc/front/feature_gate/index.html for the problem this fixes.
-
由 bors 提交于
This is a couple micro-optimizations I've been sitting on for a while. This inlines a couple functions that are important to the `std::io::mem`. Ultimately, this results in about a 15% performance increase in some micro-benchmarks for my [libserialize](https://github.com/erickt/rust-serde) rewrite.
-
由 Raphael Speyer 提交于
-
由 bors 提交于
Fixes #15080.
-
由 bors 提交于
Some cleanups I'm sick of rebasing. r? @pcwalton (do you agree with new names?)
-
由 Benjamin Herr 提交于
Unit-like structs are written as `struct Foo;`, but we erroneously accepted `struct Foo();` and took it to mean the same thing. Now we don't, so use the `struct Foo;` form! [breaking-change]
-
由 Tom Jakubowski 提交于
The #![feature(...)] line had been rendering in the docs as a header because of Markdown syntax.
-
- 22 6月, 2014 5 次提交
-
-
由 bors 提交于
There were still Total{Ord,Eq} in docs and src/etc
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Piotr Jawniak 提交于
Even if they used to test different things in the past, they are now identical to other files. Closes #11496
-
由 Niko Matsakis 提交于
infrastructure that has been accidentally left out of the build for a rather long time (it was still using `@DVec`!)
-