| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2014-10-16 | Remove libdebug and update tests. | Luqman Aden | -404/+0 | |
| 2014-10-02 | debug: remove Gc support from Repr. | Eduard Burtescu | -3/+2 | |
| 2014-08-29 | Register new snapshots | Alex Crichton | -22/+0 | |
| 2014-08-26 | Rebasing changes | Nick Cameron | -1/+1 | |
| 2014-08-26 | DST coercions and DST structs | Nick Cameron | -0/+13 | |
| [breaking-change] 1. The internal layout for traits has changed from (vtable, data) to (data, vtable). If you were relying on this in unsafe transmutes, you might get some very weird and apparently unrelated errors. You should not be doing this! Prefer not to do this at all, but if you must, you should use raw::TraitObject rather than hardcoding rustc's internal representation into your code. 2. The minimal type of reference-to-vec-literals (e.g., `&[1, 2, 3]`) is now a fixed size vec (e.g., `&[int, ..3]`) where it used to be an unsized vec (e.g., `&[int]`). If you want the unszied type, you must explicitly give the type (e.g., `let x: &[_] = &[1, 2, 3]`). Note in particular where multiple blocks must have the same type (e.g., if and else clauses, vec elements), the compiler will not coerce to the unsized type without a hint. E.g., `[&[1], &[1, 2]]` used to be a valid expression of type '[&[int]]'. It no longer type checks since the first element now has type `&[int, ..1]` and the second has type &[int, ..2]` which are incompatible. 3. The type of blocks (including functions) must be coercible to the expected type (used to be a subtype). Mostly this makes things more flexible and not less (in particular, in the case of coercing function bodies to the return type). However, in some rare cases, this is less flexible. TBH, I'm not exactly sure of the exact effects. I think the change causes us to resolve inferred type variables slightly earlier which might make us slightly more restrictive. Possibly it only affects blocks with unreachable code. E.g., `if ... { fail!(); "Hello" }` used to type check, it no longer does. The fix is to add a semicolon after the string. | ||||
| 2014-06-28 | Rename all raw pointers as necessary | Alex Crichton | -19/+22 | |
| 2014-06-24 | Remove the quad_precision_float feature gate | Alex Crichton | -7/+0 | |
| 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-15 | Register new snapshots | Alex Crichton | -20/+0 | |
| 2014-06-14 | rustc: Obsolete the `@` syntax entirely | Alex Crichton | -2/+3 | |
| This removes all remnants of `@` pointers from rustc. Additionally, this removes the `GC` structure from the prelude as it seems odd exporting an experimental type in the prelude by default. Closes #14193 [breaking-change] | ||||
| 2014-06-11 | rustc: Remove ~[T] from the language | Alex Crichton | -9/+7 | |
| The following features have been removed * box [a, b, c] * ~[a, b, c] * box [a, ..N] * ~[a, ..N] * ~[T] (as a type) * deprecated_owned_vector lint All users of ~[T] should move to using Vec<T> instead. | ||||
| 2014-05-30 | lib{std,core,debug,rustuv,collections,native,regex}: Fix snake_case errors. | Kevin Butler | -4/+5 | |
| A number of functions/methods have been moved or renamed to align better with rust standard conventions. std::reflect::MovePtrAdaptor => MovePtrAdaptor::new debug::reflect::MovePtrAdaptor => MovePtrAdaptor::new std::repr::ReprVisitor => ReprVisitor::new debug::repr::ReprVisitor => ReprVisitor::new rustuv::homing::HomingIO.go_to_IO_home => go_to_io_home [breaking-change] | ||||
| 2014-05-27 | Move std::{reflect,repr,Poly} to a libdebug crate | Alex Crichton | -0/+438 | |
| This commit moves reflection (as well as the {:?} format modifier) to a new libdebug crate, all of which is marked experimental. This is a breaking change because it now requires the debug crate to be explicitly linked if the :? format qualifier is used. This means that any code using this feature will have to add `extern crate debug;` to the top of the crate. Any code relying on reflection will also need to do this. Closes #12019 [breaking-change] | ||||
