- 28 3月, 2015 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 29 3月, 2015 10 次提交
-
-
由 bors 提交于
The collections debug helpers no longer prefix output with the collection name, in line with the current conventions for Debug implementations. Implementations that want to preserve the current behavior can simply add a `try!(write!(fmt, "TypeName "));` at the beginning of the `fmt` method. [breaking-change]
-
由 Steven Fackler 提交于
-
由 bors 提交于
Port of pcwalton removal of `#[unsafe_destructor]` check. Earlier commits impose rules on lifetimes that make generic destructors safe; thus we no longer need the `#[unsafe_destructor]` attribute nor its associated check. ---- So remove the check for the unsafe_destructor attribute. And remove outdated compile-fail tests from when lifetime-parameteric dtors were disallowed/unsafe. In addition, when one uses the attribute without the associated feature, report that the attribute is deprecated. However, I do not think this is a breaking-change, because the attribute and feature are still currently accepted by the compiler. (After the next snapshot that has this commit, we can remove the feature itself and the attribute as well.) ---- I consider this to: Fix #22196 (technically there is still the post snapshot work of removing the last remnants of the feature and the attribute, but the ticket can still be closed in my opinion).
-
由 Felix S. Klock II 提交于
Earlier commits impose rules on lifetimes that make generic destructors safe; thus we no longer need the `#[unsafe_destructor]` attribute nor its associated check. ---- So remove the check for the unsafe_destructor attribute. And remove outdated compile-fail tests from when lifetime-parameteric dtors were disallowed/unsafe. In addition, when one uses the attribute without the associated feature, report that the attribute is deprecated. However, I do not think this is a breaking-change, because the attribute and feature are still currently accepted by the compiler. (After the next snapshot that has this commit, we can remove the feature itself and the attribute as well.) ---- I consider this to: Fix #22196 (techincally there is still the post snapshot work of removing the last remants of the feature and the attribute, but the ticket can still be closed in my opinion).
-
由 Steven Fackler 提交于
-
由 bors 提交于
All methods are inlined into Iterator with `Self: Sized` bounds to make sure Iterator is still object safe. [breaking-change] This is blocked on ICEs: https://gist.github.com/sfackler/5aff7c57cf8d896e2c6f Seem to be similar to #23281.
-
由 Steven Fackler 提交于
All methods are inlined into Iterator with `Self: Sized` bounds to make sure Iterator is still object safe. [breaking-change]
-
由 Steven Fackler 提交于
Also convert [T]'s Debug impl. The behavior of the alternate flag here's changing.
-
由 Steven Fackler 提交于
The collections debug helpers no longer prefix output with the collection name, in line with the current conventions for Debug implementations. Implementations that want to preserve the current behavior can simply add a `try!(write!(fmt, "TypeName "));` at the beginning of the `fmt` method. [breaking-change]
-
由 bors 提交于
None
-
- 28 3月, 2015 29 次提交
-
-
由 Valerii Hiora 提交于
-
由 bors 提交于
- Successful merges: #23332, #23751, #23788, #23803, #23804 - Failed merges:
-
由 Manish Goregaokar 提交于
r? @steveklabnik
-
由 Manish Goregaokar 提交于
Pretty much what it says on the tin.
-
由 Manish Goregaokar 提交于
Fixes #23748
-
由 Manish Goregaokar 提交于
I found the arbitrary `10` surprising. A better method name, in such a case, would be `grow_by_10` :)
-
由 Manish Goregaokar 提交于
curl's progress meter would otherwise interfere with sudo's password prompt. In addition, add the -f flag to make sure 4xx status codes are treated as errors. r? @brson
-
由 Dan W. 提交于
r? @steveklabnik
-
由 Richo Healey 提交于
-
由 bors 提交于
The Send bound is an unnecessary restriction, and though provided as a convenience, can't be removed by downstream code. The removal of this bound is a [breaking-change] since it removes an implicit Send bound on all `E: Error` and all `Error` trait objects. To migrate, consider if your code actually requires the Send bound and, if so, add it explicitly. Fixes #23774 r? @aturon
-
由 bors 提交于
Previously a panic was generated for recursive prints due to a double-borrow of a `RefCell`. This was solved by the second borrow's output being directed towards the global stdout instead of the per-thread stdout (still experimental functionality). After this functionality was altered, however, recursive prints still deadlocked due to the overridden `write_fmt` method which locked itself first and then wrote all the data. This was fixed by removing the override of the `write_fmt` method. This means that unlocked usage of `write!` on a `Stdout`/`Stderr` may be slower due to acquiring more locks, but it's easy to make more performant with a call to `.lock()`. Closes #23781
-
由 Alex Crichton 提交于
Previously a panic was generated for recursive prints due to a double-borrow of a `RefCell`. This was solved by the second borrow's output being directed towards the global stdout instead of the per-thread stdout (still experimental functionality). After this functionality was altered, however, recursive prints still deadlocked due to the overridden `write_fmt` method which locked itself first and then wrote all the data. This was fixed by removing the override of the `write_fmt` method. This means that unlocked usage of `write!` on a `Stdout`/`Stderr` may be slower due to acquiring more locks, but it's easy to make more performant with a call to `.lock()`. Closes #23781
-
由 bors 提交于
Fixes #22716
-
由 Jonathan Reem 提交于
The Send bound is an unnecessary restriction, and though provided as a convenience, can't be removed by downstream code. The removal of this bound is a [breaking-change] since it removes an implicit Send bound on all `E: Error` and all `Error` trait objects. To migrate, consider if your code actually requires the Send bound and, if so, add it explicitly. Fixes #23774
-
由 bors 提交于
-
由 Alex Crichton 提交于
Conflicts: src/test/auxiliary/static-function-pointer-aux.rs src/test/auxiliary/trait_default_method_xc_aux.rs src/test/run-pass/issue-4545.rs
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
Conflicts: src/test/run-pass/issue-13027.rs
-
由 Steve Klabnik 提交于
Fixes #22716
-
由 Steve Klabnik 提交于
Fixes #23748
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
Fixes #21668
-
由 Alex Crichton 提交于
`std::dynamic_library` is currently using `std::old_io::Path` specifically. This change brings the API in alignment with `std::fs::File` by having it take `std::path::AsPath`. The Windows code should work, but I admittedly haven't tried it (I don't have a Windows machine readily available right now). r? @alexcrichton
-
由 Brian Anderson 提交于
Until some backwards-compatibility hazards are fixed in #23121, these need to be unstable. [breaking-change]
-
由 Alex Crichton 提交于
Fixes #23713.
-
由 Alex Crichton 提交于
Also tweaked a few things.
-
由 Alex Crichton 提交于
When testing whether a default method predicates are satisfiable, combine normalization with this check so that we also skip the default method if normalization fails. Fixes #23485. r? @nrc (I tried to address your nit from before as well)
-
由 Alex Crichton 提交于
Fixes #11794 I mostly removed superflous examples which use the standard library. I have one more quesiton here though: threads. They're mostly a library thing, at this point, right?
-