https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=cargo_update 2015-03-04T23:18:24+00:00 2015-03-04T23:18:24+00:00 David King dave@davbo.org 2015-03-04T23:18:24+00:00 urn:sha1:a037cdfcf159a6db80ddd95acd99a61b8441bbe6 Having come back to rust recently after > 6months I was looking for docs on tasks and stumbled upon this broken link. 2015-01-17T03:25:22+00:00 Tim Parenti timparenti@gmail.com 2015-01-17T03:25:22+00:00 urn:sha1:fbcc34f48339f643676a3a06c6c31a9ea47a9b8d Removes extra "the" from the phrase "the the Rust Programming Language book", which isn't particularly grammatical. 2015-01-09T08:47:09+00:00 Huon Wilson dbau.pp+github@gmail.com 2015-01-09T08:47:09+00:00 urn:sha1:4247a30bdd73ee3f1c9fa58a4130380a2e47f6ad There are hundreds of stackoverflow answers, reddit posts and blog articles that link to these documents, so it's a nicer user experience if they're not plain 404s. The intention is to let these hang around only for relatively short while. The alpha is likely to bring in many new users and they will be reading the documents mentioned above. 2015-01-08T17:02:11+00:00 Steve Klabnik steve@steveklabnik.com 2014-12-02T14:20:48+00:00 urn:sha1:16a6ebd1f60871464c731306aa9007aab30f0dbf This pulls all of our long-form documentation into a single document, nicknamed "the book" and formally titled "The Rust Programming Language." A few things motivated this change: * People knew of The Guide, but not the individual Guides. This merges them together, helping discoverability. * You can get all of Rust's longform documentation in one place, which is nice. * We now have rustbook in-tree, which can generate this kind of documentation. While its style is basic, the general idea is much better: a table of contents on the left-hand side. * Rather than a almost 10,000-line guide.md, there are now smaller files per section. 2015-01-02T06:02:59+00:00 Alex Crichton alex@alexcrichton.com 2014-12-29T23:03:01+00:00 urn:sha1:f3a7ec7028c76b3a1c6051131328f372b068e33a This pass performs a second pass of stabilization through the `std::sync` module, avoiding modules/types that are being handled in other PRs (e.g. mutexes, rwlocks, condvars, and channels). The following items are now stable * `sync::atomic` * `sync::atomic::ATOMIC_BOOL_INIT` (was `INIT_ATOMIC_BOOL`) * `sync::atomic::ATOMIC_INT_INIT` (was `INIT_ATOMIC_INT`) * `sync::atomic::ATOMIC_UINT_INIT` (was `INIT_ATOMIC_UINT`) * `sync::Once` * `sync::ONCE_INIT` * `sync::Once::call_once` (was `doit`) * C == `pthread_once(..)` * Boost == `call_once(..)` * Windows == `InitOnceExecuteOnce` * `sync::Barrier` * `sync::Barrier::new` * `sync::Barrier::wait` (now returns a `bool`) * `sync::Semaphore::new` * `sync::Semaphore::acquire` * `sync::Semaphore::release` The following items remain unstable * `sync::SemaphoreGuard` * `sync::Semaphore::access` - it's unclear how this relates to the poisoning story of mutexes. * `sync::TaskPool` - the semantics of a failing task and whether a thread is re-attached to a thread pool are somewhat unclear, and the utility of this type in `sync` is question with respect to the jobs of other primitives. This type will likely become stable or move out of the standard library over time. * `sync::Future` - futures as-is have yet to be deeply re-evaluated with the recent core changes to Rust's synchronization story, and will likely become stable in the future but are unstable until that time comes. [breaking-change] 2014-12-26T21:04:27+00:00 Steve Klabnik steve@steveklabnik.com 2014-12-26T21:04:27+00:00 urn:sha1:b8ffad5964e328340de0c03779577eb14caa16fc A part of #20038 2014-12-19T07:31:52+00:00 Aaron Turon aturon@mozilla.com 2014-12-14T08:05:32+00:00 urn:sha1:a27fbac86849e07a0a6c746869d8f78319bd3a16 This commit is part of a series that introduces a `std::thread` API to replace `std::task`. In the new API, `spawn` returns a `JoinGuard`, which by default will join the spawned thread when dropped. It can also be used to join explicitly at any time, returning the thread's result. Alternatively, the spawned thread can be explicitly detached (so no join takes place). As part of this change, Rust processes now terminate when the main thread exits, even if other detached threads are still running, moving Rust closer to standard threading models. This new behavior may break code that was relying on the previously implicit join-all. In addition to the above, the new thread API also offers some built-in support for building blocking abstractions in user space; see the module doc for details. Closes #18000 [breaking-change] 2014-12-19T07:31:51+00:00 Aaron Turon aturon@mozilla.com 2014-12-07T02:34:37+00:00 urn:sha1:43ae4b3301cc0605839778ecf59effb32b752e33 2014-12-14T09:21:57+00:00 Niko Matsakis niko@alum.mit.edu 2014-11-26T15:02:46+00:00 urn:sha1:112faabf949749488f0c2fd51098ff2feb1f6e1c cc @steveklabnick 2014-12-14T09:21:56+00:00 Niko Matsakis niko@alum.mit.edu 2014-11-26T13:12:18+00:00 urn:sha1:5c3d3989192f88b16f39d554c3844700c91b6c8e