https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.0.0-beta 2015-03-27T17:10:38+00:00 2015-03-27T17:10:38+00:00 Alex Crichton alex@alexcrichton.com 2015-03-27T17:10:38+00:00 urn:sha1:e361b25c5e0ae2b49b1850499f0c19683c843fe6 Conflicts: src/libsyntax/feature_gate.rs 2015-03-26T20:25:33+00:00 Alex Crichton alex@alexcrichton.com 2015-03-26T20:25:06+00:00 urn:sha1:9754b06cd80cfcc523573535090519bec935fec3 This commit removes compiler support for the `old_impl_check` attribute which should in theory be entirely removed now. The last remaining use of it in the standard library has been updated by moving the type parameter on the `old_io::Acceptor` trait into an associated type. As a result, this is a breaking change for all current users of the deprecated `old_io::Acceptor` trait. Code can be migrated by using the `Connection` associated type instead. [breaking-change] 2015-03-26T19:10:22+00:00 Alex Crichton alex@alexcrichton.com 2015-03-26T00:06:52+00:00 urn:sha1:43bfaa4a336095eb5697fb2df50909fd3c72ed14 Now that support has been removed, all lingering use cases are renamed. 2015-03-23T21:40:26+00:00 Brian Anderson banderson@mozilla.com 2015-03-13T22:28:35+00:00 urn:sha1:e9019101a82dd7f61dcdcd52bcc0123d5ed25d22 2015-03-21T03:07:19+00:00 Alex Crichton alex@alexcrichton.com 2015-03-17T20:33:26+00:00 urn:sha1:212e03181e422f569b6426bc08b713a9efc0d0eb 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 2015-03-13T23:25:18+00:00 Joseph Crail jbcrail@gmail.com 2015-03-13T02:42:38+00:00 urn:sha1:fcf3f3209accbb9240ea44a24165e35e50eba1d2 2015-03-12T01:11:40+00:00 Steve Klabnik steve@steveklabnik.com 2015-03-12T01:11:40+00:00 urn:sha1:64ab111b5387e9985df188a970350c9e6c7f1451 This brings comments in line with https://github.com/rust-lang/rfcs/blob/master/text/0505-api-comment-conventions.md#using-markdown 2015-03-06T18:27:28+00:00 Alex Crichton alex@alexcrichton.com 2015-02-25T21:08:51+00:00 urn:sha1:9aea749b835a6fdcad6f2840a00adac996cc0339 The `std::net` primitives should be ready for use now and as a result the old ones are now deprecated and slated for removal. Most TCP/UDP functionality is now available through `std::net` but the `std::old_io::net::pipe` module is removed entirely from the standard library. Unix socket funtionality can be found in sfackler's [`unix_socket`][unix] crate and there is currently no replacement for named pipes on Windows. [unix]: https://crates.io/crates/unix_socket [breaking-change] 2015-02-18T22:35:01+00:00 Alex Crichton alex@alexcrichton.com 2015-02-18T22:35:01+00:00 urn:sha1:5250a82f7917d6f9ec590e7e762bfd036e21ef74 Conflicts: src/librustc_trans/trans/tvec.rs 2015-02-18T22:15:43+00:00 Alex Crichton alex@alexcrichton.com 2015-02-18T06:47:40+00:00 urn:sha1:1860ee521aa6096eb7f5410a64b53311fb0d2d0e This commit is an implementation of [RFC 592][r592] and [RFC 840][r840]. These two RFCs tweak the behavior of `CString` and add a new `CStr` unsized slice type to the module. [r592]: https://github.com/rust-lang/rfcs/blob/master/text/0592-c-str-deref.md [r840]: https://github.com/rust-lang/rfcs/blob/master/text/0840-no-panic-in-c-string.md The new `CStr` type is only constructable via two methods: 1. By `deref`'ing from a `CString` 2. Unsafely via `CStr::from_ptr` The purpose of `CStr` is to be an unsized type which is a thin pointer to a `libc::c_char` (currently it is a fat pointer slice due to implementation limitations). Strings from C can be safely represented with a `CStr` and an appropriate lifetime as well. Consumers of `&CString` should now consume `&CStr` instead to allow producers to pass in C-originating strings instead of just Rust-allocated strings. A new constructor was added to `CString`, `new`, which takes `T: IntoBytes` instead of separate `from_slice` and `from_vec` methods (both have been deprecated in favor of `new`). The `new` method returns a `Result` instead of panicking. The error variant contains the relevant information about where the error happened and bytes (if present). Conversions are provided to the `io::Error` and `old_io::IoError` types via the `FromError` trait which translate to `InvalidInput`. This is a breaking change due to the modification of existing `#[unstable]` APIs and new deprecation, and more detailed information can be found in the two RFCs. Notable breakage includes: * All construction of `CString` now needs to use `new` and handle the outgoing `Result`. * Usage of `CString` as a byte slice now explicitly needs a `.as_bytes()` call. * The `as_slice*` methods have been removed in favor of just having the `as_bytes*` methods. Closes #22469 Closes #22470 [breaking-change]