https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=0.11.0 2014-06-26T06:56:49+00:00 2014-06-26T06:56:49+00:00 Piotr Jawniak sawyer47@gmail.com 2014-06-26T06:15:14+00:00 urn:sha1:f8e06c49650afd7c9ef749baa72cb8da59880f96 This commit removes superfluous to_string calls from various places 2014-06-25T04:31:19+00:00 bors bors@rust-lang.org 2014-06-25T04:31:19+00:00 urn:sha1:7a93beef7f692b34168ad69633f56483d38ad8fc The f128 type has very little support in the compiler and the feature is basically unusable today. Supporting half-baked features in the compiler can be detrimental to the long-term development of the compiler, and hence this feature is being removed. 2014-06-25T00:23:21+00:00 Keegan McAllister kmcallister@mozilla.com 2014-06-24T00:50:40+00:00 urn:sha1:5ccf056a024b0769d7adc22f57eda8d75ae07a58 2014-06-25T00:18:48+00:00 Niko Matsakis niko@alum.mit.edu 2014-04-21T21:58:52+00:00 urn:sha1:9e3d0b002a5c2e81d43351c9b8550a3f4ccfb8f9 This breaks a fair amount of code. The typical patterns are: * `for _ in range(0, 10)`: change to `for _ in range(0u, 10)`; * `println!("{}", 3)`: change to `println!("{}", 3i)`; * `[1, 2, 3].len()`: change to `[1i, 2, 3].len()`. RFC #30. Closes #6023. [breaking-change] 2014-06-24T23:36:12+00:00 Alex Crichton alex@alexcrichton.com 2014-06-24T23:34:46+00:00 urn:sha1:3d308fe65b5aa653b482341a04f301b02f263c3b The f128 type has very little support in the compiler and the feature is basically unusable today. Supporting half-baked features in the compiler can be detrimental to the long-term development of the compiler, and hence this feature is being removed. 2014-06-24T04:16:53+00:00 bors bors@rust-lang.org 2014-06-24T04:16:53+00:00 urn:sha1:768921371311430c8eb953bfdddece53a6071e6e This does not yet change the compiler and libraries from `*T` to `*const T` as it will require a snapshot to do so. cc #7362 --- Note that the corresponding RFC, https://github.com/rust-lang/rfcs/pull/68, has not yet been accepted. It was [discussed at the last meeting](https://github.com/rust-lang/rust/wiki/Meeting-weekly-2014-06-10#rfc-pr-68-unsafe-pointers-rename-t-to-const-t) and decided to be accepted, however. I figured I'd get started on the preliminary work for the RFC that will be required regardless. 2014-06-23T22:39:29+00:00 Patrick Walton pcwalton@mimiga.net 2014-06-14T02:09:12+00:00 urn:sha1:654d6444feafaa7bae17057d8b98823c7556ea14 `for...in`. Closes #14803. If you used a structure literal after one of these keywords, surround it in parentheses. [breaking-change] 2014-06-22T18:21:11+00:00 Benjamin Herr ben@0x539.de 2014-06-22T17:53:56+00:00 urn:sha1:ff50ce9a1b43720d7147251904c29b9503ea9dd9 Unit-like structs are written as `struct Foo;`, but we erroneously accepted `struct Foo();` and took it to mean the same thing. Now we don't, so use the `struct Foo;` form! [breaking-change] 2014-06-21T15:36:39+00:00 bors bors@rust-lang.org 2014-06-21T15:36:39+00:00 urn:sha1:f556c8cbd8af182a9dd871a4a36692a0dba7cc2e This will break code that looks like `Box<Trait+>`. Change that code to `Box<Trait>` instead. Closes #14925. [breaking-change] r? @brson 2014-06-20T22:46:58+00:00 Patrick Walton pcwalton@mimiga.net 2014-06-20T17:49:54+00:00 urn:sha1:ae067477fbc08e5998756d36b6ab0b82173e5c74 This will break code that looks like `Box<Trait+>`. Change that code to `Box<Trait>` instead. Closes #14925. [breaking-change]