rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2018-04-27	Don't feature gate bang macros on 'proc_macro_path_invoc'.	Sergio Benitez	-1/+0

2018-04-20	rustc: Tweak custom attribute capabilities	Alex Crichton	-0/+1
	This commit starts to lay some groundwork for the stabilization of custom attribute invocations and general procedural macros. It applies a number of changes discussed on [internals] as well as a [recent issue][issue], namely: * The path used to specify a custom attribute must be of length one and cannot be a global path. This'll help future-proof us against any ambiguities and give us more time to settle the precise syntax. In the meantime though a bare identifier can be used and imported to invoke a custom attribute macro. A new feature gate, `proc_macro_path_invoc`, was added to gate multi-segment paths and absolute paths. * The set of items which can be annotated by a custom procedural attribute has been restricted. Statements, expressions, and modules are disallowed behind two new feature gates: `proc_macro_expr` and `proc_macro_mod`. * The input to procedural macro attributes has been restricted and adjusted. Today an invocation like `#[foo(bar)]` will receive `(bar)` as the input token stream, but after this PR it will only receive `bar` (the delimiters were removed). Invocations like `#[foo]` are still allowed and will be invoked in the same way as `#[foo()]`. This is a breaking change for all nightly users as the syntax coming in to procedural macros will be tweaked slightly. * Procedural macros (`foo!()` style) can only be expanded to item-like items by default. A separate feature gate, `proc_macro_non_items`, is required to expand to items like expressions, statements, etc. Closes #50038 [internals]: https://internals.rust-lang.org/t/help-stabilize-a-subset-of-macros-2-0/7252 [issue]: https://github.com/rust-lang/rust/issues/50038
2017-02-16	Refactor macro resolution errors + add derive macro suggestions	Josh Driver	-5/+0

2017-02-05	Move derive macro expansion into the MacroExpander	Josh Driver	-3/+5
	This removes the expand_derives function, and sprinkles the functionality throughout the Invocation Collector, Expander and Resolver.
2016-05-28	Fix fallout in tests	Jeffrey Seyfried	-1/+0

2015-02-04	Deprecate in-tree `rand`, `std::rand` and `#[derive(Rand)]`.	Huon Wilson	-1/+0
	Use the crates.io crate `rand` (version 0.1 should be a drop in replacement for `std::rand`) and `rand_macros` (`#[derive_Rand]` should be a drop-in replacement). [breaking-change]
2015-01-07	Test fixes and rebase conflicts	Alex Crichton	-3/+0

2015-01-02	Use `derive` rather than `deriving` in tests	Nick Cameron	-1/+1

2014-12-23	Rename include_bin! to include_bytes!	Chris Wong	-2/+2
	According to [RFC 344][], methods that return `&[u8]` should have names ending in `bytes`. Though `include_bin!` is a macro not a method, it seems reasonable to follow the convention anyway. We keep the old name around for now, but trigger a deprecation warning when it is used. [RFC 344]: https://github.com/rust-lang/rfcs/blob/master/text/0344-conventions-galore.md [breaking-change]
2014-06-18	Deprecate the bytes!() macro.	Simon Sapin	-1/+2
	Replace its usage with byte string literals, except in `bytes!()` tests. Also add a new snapshot, to be able to use the new b"foo" syntax. The src/etc/2014-06-rewrite-bytes-macros.py script automatically rewrites `bytes!()` invocations into byte string literals. Pass it filenames as arguments to generate a diff that you can inspect, or `--apply` followed by filenames to apply the changes in place. Diffs can be piped into `tip` or `pygmentize -l diff` for coloring.
2014-04-04	rustc: feature-gate `concat_idents!`.	Huon Wilson	-1/+1
	concat_idents! is not as useful as it could be, due to macros only being allowed in limited places, and hygiene, so lets feature gate it until we make a decision about it. cc #13294
2014-03-28	Convert most code to new inner attribute syntax.	Brian Anderson	-2/+2
	Closes #2569
2014-01-27	Feature gate trace_macros.	xales	-0/+1
	Fixes #11631
2014-01-18	syntax::ext: replace span_fatal with span_err in many places.	Huon Wilson	-0/+48
	This means that compilation continues for longer, and so we can see more errors per compile. This is mildly more user-friendly because it stops users having to run rustc n times to see n macro errors: just run it once to see all of them.