rust/src/libsyntax/diagnostics/plugin.rs, branch 1.0.0-alpha

use slicing sugar

2015-01-07T22:35:56+00:00

Replace full slice notation with index calls

2015-01-06T21:46:33+00:00

More fallout

2015-01-01T21:28:19+00:00

Fallout of std::str stabilization

2014-12-22T07:31:42+00:00

librustc: Always parse `macro!()`/`macro![]` as expressions if not

2014-12-18T17:09:07+00:00

followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change]

libsyntax: use unboxed closures

2014-12-13T22:03:47+00:00

Modify libsyntax/diagnostics to not be so persnickety. The scheme

2014-12-04T15:04:51+00:00

doesn't work in a multi-crate context. We'll need to come up with something better.

std: Add a new top-level thread_local module

2014-11-24T07:37:16+00:00

This commit removes the `std::local_data` module in favor of a new `std::thread_local` module providing thread local storage. The module provides two variants of TLS: one which owns its contents and one which is based on scoped references. Each implementation has pros and cons listed in the documentation. Both flavors have accessors through a function called `with` which yield a reference to a closure provided. Both flavors also panic if a reference cannot be yielded and provide a function to test whether an access would panic or not. This is an implementation of [RFC 461][rfc] and full details can be found in that RFC. This is a breaking change due to the removal of the `std::local_data` module. All users can migrate to the new thread local system like so: thread_local!(static FOO: Rc>> = Rc::new(RefCell::new(None))) The old `local_data` module inherently contained the `Rc>>` as an implementation detail which must now be explicitly stated by users. [rfc]: https://github.com/rust-lang/rfcs/pull/461 [breaking-change]

Parse and store suffixes on literals.

2014-11-19T13:02:42+00:00

This adds an optional suffix at the end of a literal token: `"foo"bar`. An actual use of a suffix in a expression (or other literal that the compiler reads) is rejected in the parser. This doesn't switch the handling of numbers to this system, and doesn't outlaw illegal suffixes for them yet.

Switch to an independent enum for `Lit*` subtokens.

2014-11-19T01:52:31+00:00