- 14 10月, 2014 3 次提交
-
-
由 Alex Crichton 提交于
-
由 bors 提交于
This is *heavily* based on `if let` (#17634) by @jakub- and @kballard This should close #17687
-
由 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.
-
- 13 10月, 2014 12 次提交
-
-
由 bors 提交于
-
由 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 提交于
-
由 bors 提交于
Fixes #17933.
-
由 bors 提交于
I did not put the crate name in the error note, if that's necessary I'll look into it. Closes #17709
-
由 bors 提交于
[breaking-change]
-
由 Felix Raimundo 提交于
#17709
-
由 bors 提交于
Fixes #17877.
-
由 Ziad Hatahet 提交于
`strftime` currently returns a `String`. This does not indicate that this function may return an error due to to a malformed format string. This change introduces a `ParseError` enum which indicates the type of error that occurred. The return type of `strptime` was also changed to use this new enum instead of returning `Result<String, String>`. Now, all instances where `strftime` was used need to have their return value checked to see if it were valid or not. [breaking-change]
-
由 Steven Fackler 提交于
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".
-
由 Jakub Wieczorek 提交于
Doing so would incur deeply nested expansion of the tree with no useful side effects. This is problematic for "wide" data types such as structs with dozens of fields but where only a few are actually being matched or bound. Most notably, matching a fixed slice would use a number of stack frames that grows with the number of elements in the slice. Fixes #17877.
-
- 12 10月, 2014 15 次提交
-
-
由 Daniel Micay 提交于
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.
-
由 Jakub Wieczorek 提交于
Fixes #17933.
-
由 bors 提交于
Closes #17861.
-
由 OGINO Masanori 提交于
Signed-off-by: NOGINO Masanori <masanori.ogino@gmail.com>
-
由 bors 提交于
This converts old style cfgs that generate warnings during `make check` to the new syntax.
-
由 bors 提交于
[breaking-change] Closes #17916
-
由 bors 提交于
Some examples: - `std::slice::slice`: [before](http://validator.w3.org/check?uri=http%3A%2F%2Fdoc.rust-lang.org%2Fstd%2Fslice%2Fprimitive.slice.html&charset=%28detect+automatically%29&doctype=Inline&group=0) and [after](http://validator.w3.org/check?uri=http%3A%2F%2Fnodakai.github.io%2Frust-f40b60b-doc%2Fstd%2Fslice%2Fprimitive.slice.html&charset=%28detect+automatically%29&doctype=Inline&group=0) - `core::char::char`: [before](http://validator.w3.org/check?uri=http%3A%2F%2Fdoc.rust-lang.org%2Fcore%2Fchar%2Fprimitive.char.html&charset=%28detect+automatically%29&doctype=Inline&group=0) and [after](http://validator.w3.org/check?uri=http%3A%2F%2Fnodakai.github.io%2Frust-f40b60b-doc%2Fcore%2Fchar%2Fprimitive.char.html&charset=%28detect+automatically%29&doctype=Inline&group=0) - `hexfloat::expand_syntax_ext`: [before](http://validator.w3.org/check?uri=http%3A%2F%2Fdoc.rust-lang.org%2Fhexfloat%2Ffn.expand_syntax_ext.html&charset=%28detect+automatically%29&doctype=Inline&group=0) and [after](http://validator.w3.org/check?uri=http%3A%2F%2Fnodakai.github.io%2Frust-f40b60b-doc%2Fhexfloat%2Ffn.expand_syntax_ext.html&charset=%28detect+automatically%29&doctype=Inline&group=0) TODO: do the same for tuples.
-
由 Guillaume Pinot 提交于
-
由 bors 提交于
I previously avoided `#[inline]`ing anything assuming someone would come in and explain to me where this would be appropriate. Apparently no one *really* knows, so I'll just go the opposite way an inline everything assuming someone will come in and yell at me that such-and-such shouldn't be `#[inline]`. ================== For posterity, iteration comparisons: ``` test btree::map::bench::iter_20 ... bench: 971 ns/iter (+/- 30) test btree::map::bench::iter_1000 ... bench: 29445 ns/iter (+/- 480) test btree::map::bench::iter_100000 ... bench: 2929035 ns/iter (+/- 21551) test treemap::bench::iter_20 ... bench: 530 ns/iter (+/- 66) test treemap::bench::iter_1000 ... bench: 26287 ns/iter (+/- 825) test treemap::bench::iter_100000 ... bench: 7650084 ns/iter (+/- 356711) test trie::bench_map::iter_20 ... bench: 646 ns/iter (+/- 265) test trie::bench_map::iter_1000 ... bench: 43556 ns/iter (+/- 5014) test trie::bench_map::iter_100000 ... bench: 12988002 ns/iter (+/- 139676) ``` As you can see `btree` "scales" much better than `treemap`. `triemap` scales quite poorly. Note that *completely* different results are given if the elements are inserted in order from the range [0, size]. In particular, TrieMap *completely* dominates in the sorted case. This suggests adding benches for both might be worthwhile. However unsorted is *probably* the more "normal" case, so I consider this "good enough" for now.
-
由 Jakub Wieczorek 提交于
-
由 Jakub Wieczorek 提交于
-
由 Jakub Wieczorek 提交于
-
由 Michael Gehring 提交于
-
由 Michael Gehring 提交于
-
由 John Gallagher 提交于
-
- 11 10月, 2014 10 次提交
-
-
由 bors 提交于
compiletest needs to link to native crate, or at least the `rt` library. (I tried using a dependency on `rustrt` instead, and that did not resolve the problem. But this does.) Partially addresses #17883
-
由 Michael Gehring 提交于
-
由 Boris Egorov 提交于
[breaking-change] Closes #17916
-
由 Felix S. Klock II 提交于
(I tried using a dependency on `rustrt` instead, and that did not resolve the problem. But this does.) Fix #17883
-
由 bors 提交于
Also convert a number of `static mut` to just a plain old `static` and remove some unsafe blocks.
-
由 bors 提交于
Now that libgreen is gone, this is all wrong. Fixes #17923
-
由 Alex Crichton 提交于
Also convert a number of `static mut` to just a plain old `static` and remove some unsafe blocks.
-
由 bors 提交于
Only one warning remain, and I can't find a way to remove it without doing more bound checks: ``` shootout-nbody.rs:105:36: 105:51 warning: use of deprecated item: use iter_mut, #[warn(deprecated)] on by default shootout-nbody.rs:105 let bi = match b_slice.mut_shift_ref() { ``` using `split_at_mut` may be an option, but it will do more bound checking. If anyone have an idea, I'll update this PR.
-
由 John Gallagher 提交于
Closes #17687
-
由 John Gallagher 提交于
-