| Age | Commit message (Collapse) | Author | Lines |
|---|
|
r=steveklabnik
This is the first use of `box`. It's an unstable feature and also isn't
consistent with the use of `Box` in the "original" code above it.
r? @steveklabnik
|
|
Create a new section under the Unstable section for `box` syntax and
patterns and removed their discussion from the Pointers section.
|
|
Conflicts:
src/test/compile-fail/coherence-impls-copy.rs
|
|
Fix example and some text for: `read_line` takes `&mut String` and return `Result` instead `IoResult`.
r? @steveklabnik
|
|
|
|
|
|
Fix example and some text for: `read_line` takes `&mut String` and return `Result` instead `IoResult`.
|
|
Fixes #23688
r? @alexcrichton
|
|
Fixes #23688
|
|
Fixes #23881
|
|
Fixes #23881
|
|
This is a deprecated attribute that is slated for removal, and it also affects
all implementors of the trait. This commit removes the attribute and fixes up
implementors accordingly. The primary implementation which was lost was the
ability to compare `&[T]` and `Vec<T>` (in that order).
This change also modifies the `assert_eq!` macro to not consider both directions
of equality, only the one given in the left/right forms to the macro. This
modification is motivated due to the fact that `&[T] == Vec<T>` no longer
compiles, causing hundreds of errors in unit tests in the standard library (and
likely throughout the community as well).
Closes #19470
[breaking-change]
|
|
|
|
|
|
This commit cleans out a large amount of deprecated APIs from the standard
library and some of the facade crates as well, updating all users in the
compiler and in tests as it goes along.
|
|
|
|
This is a deprecated attribute that is slated for removal, and it also affects
all implementors of the trait. This commit removes the attribute and fixes up
implementors accordingly. The primary implementation which was lost was the
ability to compare `&[T]` and `Vec<T>` (in that order).
This change also modifies the `assert_eq!` macro to not consider both directions
of equality, only the one given in the left/right forms to the macro. This
modification is motivated due to the fact that `&[T] == Vec<T>` no longer
compiles, causing hundreds of errors in unit tests in the standard library (and
likely throughout the community as well).
cc #19470
[breaking-change]
|
|
|
|
r=alexcrichton
This makes some use of `x` and `y`, instead of setting them to the same value.
|
|
The documentation says that 'The current convention is to use the `test` module
to hold your "unit-style"' but then defines the module as "tests" instead.
Also in the output of the command we can see:
```
test test::it_works ... ok
```
So I think the name of the module was meant to be "test"
|
|
Fixes #19733
|
|
|
|
|
|
|
|
- Successful merges: #23746, #23836, #23852
- Failed merges: #23855
|
|
Fixes #19733
|
|
|
|
Remove the last sentence about standard io chapter.
Additional Fixes #23760
|
|
With help of https://github.com/lucasdemarchi/codespell
r? @steveklabnik
|
|
The documentation says that 'The current convention is to use the `test` module
to hold your "unit-style"' but then defines the module as "tests" instead.
|
|
arrays-vectors-and-slices chapter)
Remove the last sentence about standard io chapter.
Additional Fixes #23760
|
|
|
|
|
|
This was originally used to set up the guessing game, but that no longer
exists. This version uses `old_io`, and updating it involves talking
about `&mut` and such, which we haven't covered yet. So, for now, let's
just remove it.
Fixes #23760
|
|
|
|
r? @steveklabnik
|
|
Fixes #23748
|
|
I found the arbitrary `10` surprising. A better method name, in such a case, would be `grow_by_10` :)
|
|
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
|
|
r? @steveklabnik
|
|
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
|
|
Conflicts:
src/test/run-pass/issue-13027.rs
|
|
Fixes #23748
|
|
Until some backwards-compatibility hazards are fixed in #23121,
these need to be unstable.
[breaking-change]
|
|
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?
|
|
|
|
|
|
Conflicts:
src/librustc/middle/ty.rs
src/librustc_trans/trans/adt.rs
src/librustc_typeck/check/mod.rs
src/libserialize/json.rs
src/test/run-pass/spawn-fn.rs
|
|
|
|
|
