https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2014-11-21T01:19:13+00:00 2014-11-21T01:19:13+00:00 Aaron Turon aturon@mozilla.com 2014-11-14T21:55:57+00:00 urn:sha1:3ee916e50bd86768cb2a9141f9b2c52d2601b412 With runtime removal complete, there's nothing left of libnative. This commit removes it. Fixes #18687 [breaking-change] 2014-11-06T16:03:18+00:00 Aaron Turon aturon@mozilla.com 2014-11-03T01:04:32+00:00 urn:sha1:cfafc1b7377d34d8c60db7cd386836d39b80af41 This commit renames a number of extension traits for slices and string slices, now that they have been refactored for DST. In many cases, multiple extension traits could now be consolidated. Further consolidation will be possible with generalized where clauses. The renamings are consistent with the [new `-Prelude` suffix](https://github.com/rust-lang/rfcs/pull/344). There are probably a few more candidates for being renamed this way, but that is left for API stabilization of the relevant modules. Because this renames traits, it is a: [breaking-change] However, I do not expect any code that currently uses the standard library to actually break. Closes #17917 2014-10-29T15:43:07+00:00 Steve Klabnik steve@steveklabnik.com 2014-10-09T19:17:22+00:00 urn:sha1:7828c3dd2858d8f3a0448484d8093e22719dbda0 https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] 2014-10-20T15:17:33+00:00 Alex Crichton alex@alexcrichton.com 2014-10-19T20:00:32+00:00 urn:sha1:96445a533e8ea40701e2a9bbd25347141e63c115 2014-10-19T19:59:40+00:00 Alex Crichton alex@alexcrichton.com 2014-10-15T06:05:01+00:00 urn:sha1:9d5d97b55d6487ee23b805bc1acbaa0669b82116 Spring cleaning is here! In the Fall! This commit removes quite a large amount of deprecated functionality from the standard libraries. I tried to ensure that only old deprecated functionality was removed. This is removing lots and lots of deprecated features, so this is a breaking change. Please consult the deprecation messages of the deleted code to see how to migrate code forward if it still needs migration. [breaking-change] 2014-10-11T05:09:49+00:00 Alex Crichton alex@alexcrichton.com 2014-10-11T04:59:10+00:00 urn:sha1:dae48a07f34dcf714b3b57029f4e03a0b95a269e Also convert a number of `static mut` to just a plain old `static` and remove some unsafe blocks. 2014-10-02T19:16:37+00:00 Benjamin Herr ben@0x539.de 2014-10-02T18:55:26+00:00 urn:sha1:af633ce157082bf2b0fd0577765e9b49c34c3e90 The bitshifts were wrong in that they invoked undefined behavior and only passed the lower byte of the presumed-to-be-32bit errno value. Apparently all actually possible values for errno happen to be easily under 256, so this didn't cause any actual problems. This commit fixes the bitshifts, but doesn't generalize to errno types that aren't 32bit. 2014-09-30T19:52:47+00:00 Steven Fackler sfackler@gmail.com 2014-09-29T07:28:50+00:00 urn:sha1:d3444779e6776025ee19202c5e69964abde90374 2014-09-16T21:37:48+00:00 Aaron Turon aturon@mozilla.com 2014-09-15T03:27:36+00:00 urn:sha1:fc525eeb4ec3443d29bce677f589b19f31c189bb 2014-09-13T09:07:39+00:00 Patrick Walton pcwalton@mimiga.net 2014-09-11T05:26:41+00:00 urn:sha1:467bea04fa1d5fd894d64b2b2901d94260301631 type they provide an implementation for. This breaks code like: mod foo { struct Foo { ... } } impl foo::Foo { ... } Change this code to: mod foo { struct Foo { ... } impl Foo { ... } } Additionally, if you used the I/O path extension methods `stat`, `lstat`, `exists`, `is_file`, or `is_dir`, note that these methods have been moved to the the `std::io::fs::PathExtensions` trait. This breaks code like: fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Change this code to: use std::io::fs::PathExtensions; fn is_it_there() -> bool { Path::new("/foo/bar/baz").exists() } Closes #17059. RFC #155. [breaking-change]