- 24 3月, 2015 1 次提交
-
-
由 Brian Anderson 提交于
The variable '$SHELL' is not actually defined by 'sh'.
-
- 22 3月, 2015 1 次提交
-
-
由 bors 提交于
After this patch code like `let ref a = *"abcdef"` doesn't cause ICE anymore. Required for #23121 There are still places in rustc_trans where pointers are always assumed to be thin. In particular, #19064 is not resolved by this patch.
-
- 21 3月, 2015 6 次提交
-
-
由 bors 提交于
This commit removes the reexports of `old_io` traits as well as `old_path` types and traits from the prelude. This functionality is now all deprecated and needs to be removed to make way for other functionality like `Seek` in the `std::io` module (currently reexported as `NewSeek` in the io prelude). Closes #23377 Closes #23378
-
由 Alex Crichton 提交于
This commit removes the reexports of `old_io` traits as well as `old_path` types and traits from the prelude. This functionality is now all deprecated and needs to be removed to make way for other functionality like `Seek` in the `std::io` module (currently reexported as `NewSeek` in the io prelude). Closes #23377 Closes #23378
-
由 bors 提交于
because then the call to `unwrap()` will not print the error object.
-
由 Alex Crichton 提交于
This reverts commit aec67c2e.
-
由 bors 提交于
Resolved #21773. (Aarch64 test has been broken again) r? @alexcrichton
-
- 20 3月, 2015 32 次提交
-
-
由 bors 提交于
Fixes #22551 ('grammar' wasn't really used in the chapter at all)
-
由 Steve Klabnik 提交于
Fixes #22551
-
由 bors 提交于
When investigating #22518, this chapter is really the only part that has `rand`, and the rest still works without it. We should have some examples like this, but for now, it's more important to be right than perfect.
-
由 Oliver Schneider 提交于
-
由 bors 提交于
-
由 Manish Goregaokar 提交于
As @alexcrichton says, this was really a libgreen thing, and isn't relevant now. As this removes a technically-public function, this is a [breaking-change]
-
由 Manish Goregaokar 提交于
Fixes #22002
-
由 Manish Goregaokar 提交于
Fixes #16330 My troff is probably poor, so make sure that all looks okay.
-
由 Manish Goregaokar 提交于
`uppercase` and `lowercase` are currently named `to_uppercase` and `to_lowercase`. Also adds a link to the `char` type documentation which has much more detail on these iterators.
-
由 Manish Goregaokar 提交于
This fixes several use cases that were broken after #23265 landed.
-
由 Manish Goregaokar 提交于
The wiki doesn't seem to exist
-
由 Manish Goregaokar 提交于
Multiple people have been suprised by this aspect of read_line's behavior, which is not obvious from the docs.
-
由 Manish Goregaokar 提交于
These two borrowing examples were confusing/misleading. This changes it to more clearly show how you _can_ borrow a box, and also uses & instead of &*.
-
由 Manish Goregaokar 提交于
Fixes #22098.
-
由 Manish Goregaokar 提交于
Fixes #21709
-
由 Manish Goregaokar 提交于
Fixes #23426
-
由 Manish Goregaokar 提交于
We don't use 'task' anymore, these are now threads. Because this changes the name of a compiler option, this is [breaking-change] I think this is small enough to not need an RFC, nor a period of accepting both. If we want to take both for a while, I can change the patch.
-
由 Manish Goregaokar 提交于
The IP and socket address types all had `FromStr` implemented but the implementations were not marked stable, nor was the error type returned ready to be properly stabilized. This commit marks the implementations of `FromStr` as stable and also renamed the `ParseError` structure to `AddrParseError`. The error is now also an opaque structure that cannot be constructed outside the standard library. cc #22949 [breaking-change]
-
由 bors 提交于
The IP and socket address types all had `FromStr` implemented but the implementations were not marked stable, nor was the error type returned ready to be properly stabilized. This commit marks the implementations of `FromStr` as stable and also renamed the `ParseError` structure to `AddrParseError`. The error is now also an opaque structure that cannot be constructed outside the standard library. cc #22949 [breaking-change]
-
由 bors 提交于
This was added for #23241.
-
由 Steve Klabnik 提交于
As @alexcrichton says, this was really a libgreen thing, and isn't relevant now. As this removes a technically-public function, this is a [breaking-change] Conflicts: src/libtest/lib.rs
-
由 Manish Goregaokar 提交于
This was added for #23241.
-
由 Manish Goregaokar 提交于
This should solve issues #23115, #23469, and #23407. As the title says, this is just a workaround. The underlying problem is that macro expansion can produce invalid spans. I've opened issue #23480 so we don't forget about that.
-
由 Steve Klabnik 提交于
Fixes #16330
-
由 bors 提交于
This should solve issues #23115, #23469, and #23407. As the title says, this is just a workaround. The underlying problem is that macro expansion can produce invalid spans. I've opened issue #23480 so we don't forget about that.
-
由 Steve Klabnik 提交于
Fixes #23426
-
由 Steve Klabnik 提交于
Fixes #22002
-
由 Steve Klabnik 提交于
Fixes #21709
-
由 Matt Brubeck 提交于
`uppercase` and `lowercase` are currently named `to_uppercase` and `to_lowercase`. Also adds a link to the `char` type documentation which has much more detail on these iterators.
-
由 Steve Klabnik 提交于
We don't use 'task' anymore, these are now threads. Because this changes the name of a compiler option, this is [breaking-change]
-
由 Steve Klabnik 提交于
Fixes #22518
-
由 bors 提交于
This commit stabilizes the `ErrorKind` enumeration which is consumed by and generated by the `io::Error` type. The purpose of this type is to serve as a cross-platform namespace to categorize errors into. Two specific issues are addressed as part of this stablization: * The naming of each variant was scrutinized and some were tweaked. An example is how `FileNotFound` was renamed to simply `NotFound`. These names should not show either a Unix or Windows bias and the set of names is intended to grow over time. For now the names will likely largely consist of those errors generated by the I/O APIs in the standard library. * The mapping of OS error codes onto kinds has been altered. Coalescing no longer occurs (multiple error codes become one kind). It is intended that each OS error code, if bound, corresponds to only one `ErrorKind`. The current set of error kinds was expanded slightly to include some networking errors. This commit also adds a `raw_os_error` function which returns an `Option<i32>` to extract the underlying raw error code from the `Error`. Closes #16666 [breaking-change]
-