- 15 10月, 2014 2 次提交
- 14 10月, 2014 32 次提交
-
-
由 bors 提交于
Fix issue #17999 (Unused variables inside `for` are not detected)
-
由 Ms2ger 提交于
-
由 bors 提交于
-
由 Chris Morgan 提交于
-
由 Chris Morgan 提交于
-
由 Chris Morgan 提交于
This wasn’t really consistent with other things; the last section of the import was not highlighted in any other case. Also `use {foo, bar};` was having the foo and bar not highlighted, where they would have been as separate statements.
-
由 bors 提交于
The Sieve algorithm only requires checking all elements up to and including the square root of the maximum prime you're looking for. After that, the remaining elements are guaranteed to be prime.
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 bors 提交于
The Windows-specific instruction under 'Quick Start' linked the wiki article on getting started developing Rust itself, but the quick start is just about obtaining a working Rust installation. The actual wiki page with Windows-specific instructions was difficult to find. The most important thing to note on Windows is that you need mingw-builds, and it is totally not obvious. The only place where I have seen it mentioned is the wiki page, which was difficult to find before.
-
由 Falco Hirschenberger 提交于
-
由 Stefan Bucur 提交于
-
由 bors 提交于
This is *heavily* based on `if let` (#17634) by @jakub- and @kballard This should close #17687
-
由 Felix S. Klock II 提交于
```- To reproduce issue on commit ba246100 it does not suffice to add just `check-build-compiletest` to `check-secondary`; one must also ensure that `check-build-compiletest` precedes the satisification of the `check` rule. Otherwise hidden dependencies of `compiletest` would end up getting satisfied when make builds `rustc` at each stage in order to eventually run `check-stage2`. So to handle that I moved `check-secondary` before `check` in the `check-all` rule that bors uses, and for good measure, I also put `check-build-compiltest` at the front of the `check-secondary` rule's dependencies. My understanding is that running `check-secondary` should be relatively cheap, and thus such a reordering will not hurt bors. ``` - Fix #17883.
-
由 Alex Crichton 提交于
Turns out you can create &'static T quite easily in a constant, I just forgot about this!
-
由 bors 提交于
Added 64-bit Windows support to the list of platforms. Support for 64-bit Windows was added in Rust 0.12.0. See https://mail.mozilla.org/pipermail/rust-dev/2014-October/011267.html for the release notes.
-
由 Steven Fackler 提交于
Closes #17990
-
- 13 10月, 2014 6 次提交
-
-
由 bors 提交于
-
由 Björn Steinbrink 提交于
Function arguments are (hopefully!) the last places where allocas don't get proper markers for the end of their lifetimes. This means that this code using 64 bytes of stack for the function arguments: ````rust std::io::println("1"); std::io::println("2"); std::io::println("3"); std::io::println("4"); ```` But with the proper lifetime markers, the slots can be reused, and the arguments only need 16 bytes of stack.
-
由 Simon Sapin 提交于
-
由 bors 提交于
All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and".
-
由 bors 提交于
Position independent code has fewer requirements in executables, so pass the appropriate flag to LLVM in order to allow more optimization. At the moment this means faster thread-local storage.
-
由 bors 提交于
-