https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2015-09-11T18:19:20+00:00 2015-09-11T18:19:20+00:00 Alex Crichton alex@alexcrichton.com 2015-09-08T22:53:46+00:00 urn:sha1:f4be2026dfb507e5db919cc5df8fd934e05fa0b8 This commit does some refactoring to make almost all of the `std::rt` private. Specifically, the following items are no longer part of its API: * DEFAULT_ERROR_CODE * backtrace * unwind * args * at_exit * cleanup * heap (this is just alloc::heap) * min_stack * util The module is now tagged as `#[doc(hidden)]` as the only purpose it's serve is an entry point for the `panic!` macro via the `begin_unwind` and `begin_unwind_fmt` reexports. 2015-09-03T00:21:11+00:00 Alex Crichton alex@alexcrichton.com 2015-08-28T17:50:16+00:00 urn:sha1:04c09f9466c57dca50c643c6099c0f9957d62220 This adds a call to `rt::cleanup` on `process::exit` to make sure we clean up after ourselves on the way out from Rust. Closes #28065 2015-08-11T22:11:13+00:00 Alex Crichton alex@alexcrichton.com 2015-08-11T21:31:23+00:00 urn:sha1:938099a7ebccbad2a2cad58d71df316d5ccd512c * Lots of core prelude imports removed * Makefile support for MSVC env vars and Rust crates removed * Makefile support for morestack removed 2015-08-04T00:23:01+00:00 Alex Crichton alex@alexcrichton.com 2015-07-30T00:01:14+00:00 urn:sha1:5cccf3cd256420d9f32c265e83036dea1d5f94d8 This commit is an implementation of [RFC 1184][rfc] which tweaks the behavior of the `#![no_std]` attribute and adds a new `#![no_core]` attribute. The `#![no_std]` attribute now injects `extern crate core` at the top of the crate as well as the libcore prelude into all modules (in the same manner as the standard library's prelude). The `#![no_core]` attribute disables both std and core injection. [rfc]: https://github.com/rust-lang/rfcs/pull/1184 2015-07-02T02:09:14+00:00 Alex Newman posix4e@gmail.com 2015-07-01T03:37:11+00:00 urn:sha1:0b7c4f57f6ba59dabe4db2808fe45e8bd8bbce22 2015-05-27T08:19:03+00:00 Eduard Burtescu edy.burt@gmail.com 2015-05-27T08:18:36+00:00 urn:sha1:377b0900aede976b2d37a499bbd7b62c2e39b358 2015-03-31T22:49:57+00:00 Alex Crichton alex@alexcrichton.com 2015-03-30T18:00:05+00:00 urn:sha1:d4a2c941809f303b97d153e06ba07e95cd245f88 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. 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-02-21T09:20:48+00:00 bors bors@rust-lang.org 2015-02-21T09:20:48+00:00 urn:sha1:2b01a37ec38db9301239f0c0abcf3c695055b0ff This patch adds the necessary pieces to support rust on Bitrig https://bitrig.org 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]