rust/src/libsyntax/ext/log_syntax.rs, branch perf-tmp

Move built-in syntax extensions to a separate crate

2015-12-15T06:04:46+00:00

Allow tracking issues for lang features.

2015-09-08T01:01:42+00:00

This is similar to the libs version, which allow an `issue` field in the `#[unstable]` attribute. cc #28244

Remove the vestigial ExtCtxt::print_backtrace function.

2015-04-11T23:48:52+00:00

It was added in 2011-08-05 and reduced to a no-op ten days later.

Address the other cases of #22234; fix #22234.

2015-02-16T00:36:06+00:00

The other cases: `concat_idents!`, `log_syntax!`, and `trace_macros!`, (these macros, with `asm!`, are handled (eagerly) in feature_gate.rs).

Add Span and separate open/close delims to TTDelim

2014-10-25T22:53:29+00:00

This came up when working [on the gl-rs generator extension](https://github.com/bjz/gl-rs/blob/990383de801bd2e233159d5be07c9b5622827620/src/gl_generator/lib.rs#L135-L146). The new definition of `TTDelim` adds an associated `Span` that covers the whole token tree and enforces the invariant that a delimited sequence of token trees must have an opening and closing delimiter. A `get_span` method has also been added to `TokenTree` type to make it easier to implement better error messages for syntax extensions.

Implement generalized object and type parameter bounds (Fixes #16462)

2014-08-28T01:46:52+00:00

std: Rename the `ToStr` trait to `ToString`, and `to_str` to `to_string`.

2014-07-08T20:01:43+00:00

[breaking-change]

librustc: Remove `~EXPR`, `~TYPE`, and `~PAT` from the language, except

2014-05-07T06:12:54+00:00

for `~str`/`~[]`. Note that `~self` still remains, since I forgot to add support for `Box` before the snapshot. How to update your code: * Instead of `~EXPR`, you should write `box EXPR`. * Instead of `~TYPE`, you should write `Box`. * Instead of `~PATTERN`, you should write `box PATTERN`. [breaking-change]

syntax: unify all MacResult's into a single trait.

2014-04-16T07:53:27+00:00

There's now one unified way to return things from a macro, instead of being able to choose the `AnyMacro` trait or the `MRItem`/`MRExpr` variants of the `MacResult` enum. This does simplify the logic handling the expansions, but the biggest value of this is it makes macros in (for example) type position easier to implement, as there's this single thing to modify. By my measurements (using `-Z time-passes` on libstd and librustc etc.), this appears to have little-to-no impact on expansion speed. There are presumably larger costs than the small number of extra allocations and virtual calls this adds (notably, all `macro_rules!`-defined macros have not changed in behaviour, since they had to use the `AnyMacro` trait anyway).

De-@ TokenTree.

2014-03-28T16:28:04+00:00