https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2013-12-17T01:47:11+00:00 2013-12-17T01:47:11+00:00 Alex Crichton alex@alexcrichton.com 2013-12-06T02:19:06+00:00 urn:sha1:529e268ab900f1b6e731af64ce2aeecda3555f4e 2013-12-11T18:54:06+00:00 Erik Price erik.price16@gmail.com 2013-12-10T07:16:18+00:00 urn:sha1:5731ca3078318a66a13208133d8839a9f9f92629 Also remove all instances of 'self within the codebase. This fixes #10889. 2013-12-10T23:13:12+00:00 Patrick Walton pcwalton@mimiga.net 2013-12-05T00:06:55+00:00 urn:sha1:f08f3a757643aa16b05ec7dee73ecff216354ddf their `finally` blocks to RAII. 2013-12-10T23:13:12+00:00 Patrick Walton pcwalton@mimiga.net 2013-12-04T22:43:02+00:00 urn:sha1:ab3bec91d77150e434ac1480fbb3935213e33dca `deschedule_running_task_and_then`. 2013-11-26T19:04:39+00:00 Patrick Walton pcwalton@mimiga.net 2013-11-24T19:44:28+00:00 urn:sha1:9521551b4710805674ad6c1755bef4e76784db02 2013-11-26T16:25:27+00:00 Patrick Walton pcwalton@mimiga.net 2013-11-22T01:23:21+00:00 urn:sha1:f571e46ddb696d15a8cc912309714ca74f23dcc4 compile-fail tests, run-fail tests, and run-pass tests. 2013-11-26T16:23:57+00:00 Patrick Walton pcwalton@mimiga.net 2013-11-20T22:17:12+00:00 urn:sha1:1eca34de7dd55719cd83153994e5caf2027f62a2 2013-11-25T05:21:12+00:00 Alex Crichton alex@alexcrichton.com 2013-11-22T00:55:40+00:00 urn:sha1:acca9e3834842ee8d8104abe9b8b9bb88861793c The reasons for doing this are: * The model on which linked failure is based is inherently complex * The implementation is also very complex, and there are few remaining who fully understand the implementation * There are existing race conditions in the core context switching function of the scheduler, and possibly others. * It's unclear whether this model of linked failure maps well to a 1:1 threading model Linked failure is often a desired aspect of tasks, but we would like to take a much more conservative approach in re-implementing linked failure if at all. Closes #8674 Closes #8318 Closes #8863 2013-10-28T20:14:42+00:00 Alex Crichton alex@alexcrichton.com 2013-10-22T22:09:23+00:00 urn:sha1:5dd1583c57fbee9a07ac1111858871c241a24c50 Primarily this makes the Scheduler and all of its related interfaces public. The reason for doing this is that currently any extern event loops had no access to the scheduler at all. This allows third-party event loops to manipulate the scheduler, along with allowing the uv event loop to live inside of its own crate. 2013-10-25T06:49:11+00:00 Alex Crichton alex@alexcrichton.com 2013-10-22T22:00:37+00:00 urn:sha1:64a5c3bc1ee869990f8205374f9dac837a475dbd It's not guaranteed that there will always be an event loop to run, and this implementation will serve as an incredibly basic one which does not provide any I/O, but allows the scheduler to still run. cc #9128