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

Age	Commit message (Collapse)	Author	Lines
2020-07-27	mv std libs to library/	mark	-407/+0

2020-07-26	proc_macro: Add API for tracked access to environment variables	Vadim Petrochenkov	-0/+4

2020-05-15	Fix {:#?} representation of proc_macro::Literal	David Tolnay	-2/+3
	Before: TokenStream [ Ident { ident: "name", span: #0 bytes(37..41), }, Punct { ch: '=', spacing: Alone, span: #0 bytes(42..43), }, Literal { lit: Lit { kind: Str, symbol: "SNPP", suffix: None }, span: Span { lo: BytePos(44), hi: BytePos(50), ctxt: #0 } }, Punct { ch: ',', spacing: Alone, span: #0 bytes(50..51), }, Ident { ident: "owner", span: #0 bytes(56..61), }, Punct { ch: '=', spacing: Alone, span: #0 bytes(62..63), }, Literal { lit: Lit { kind: Str, symbol: "Canary M Burns", suffix: None }, span: Span { lo: BytePos(64), hi: BytePos(80), ctxt: #0 } }, ] After: TokenStream [ Ident { ident: "name", span: #0 bytes(37..41), }, Punct { ch: '=', spacing: Alone, span: #0 bytes(42..43), }, Literal { kind: Str, symbol: "SNPP", suffix: None, span: #0 bytes(44..50), }, Punct { ch: ',', spacing: Alone, span: #0 bytes(50..51), }, Ident { ident: "owner", span: #0 bytes(56..61), }, Punct { ch: '=', spacing: Alone, span: #0 bytes(62..63), }, Literal { kind: Str, symbol: "Canary M Burns", suffix: None, span: #0 bytes(64..80), }, ]
2019-12-22	Format the world	Mark Rousskov	-5/+2

2019-10-03	proc_macro: Add `Span::mixed_site` exposing `macro_rules` hygiene	Vadim Petrochenkov	-0/+1

2019-03-27	Auto merge of #55780 - ogoffart:span_source_text, r=petrochenkov	bors	-0/+1
	Introduce proc_macro::Span::source_text A function to extract the actual source behind a Span. Background: I would like to use `syn` in a `build.rs` script to parse the rust code, and extract part of the source code. However, `syn` only gives access to proc_macro2::Span, and i would like to get the source code behind that. I opened an issue on proc_macro2 bug tracker for this feature https://github.com/alexcrichton/proc-macro2/issues/110 and @alexcrichton said the feature should first go upstream in proc_macro. So there it is! Since most of the Span API is unstable anyway, this is guarded by the same `proc_macro_span` feature as everything else.
2019-02-24	Use ? in some macros	Taiki Endo	-3/+3

2019-02-04	libproc_macro => 2018	Taiki Endo	-4/+4

2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2018-12-07	Various minor/cosmetic improvements to code	Alexander Regueiro	-1/+1

2018-12-01	Introduce proc_macro::Span::source_text	Olivier Goffart	-0/+1

2018-11-30	proc_macro: introduce a "bridge" between clients (proc macros) and servers ↵	Eduard-Mihai Burtescu	-0/+413
	(compiler front-ends).