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

Age	Commit message (Collapse)	Author	Lines
2019-10-28	Fix a previously forgotten pretty-printing test after a change to the ↵	Patryk Wychowaniec	-1/+1
	pretty-printing mechanism.
2019-09-15	Print visibility of `macro` items	Matthew Jasper	-1/+1

2019-08-25	pprust: Do not print spaces before some tokens	Vadim Petrochenkov	-9/+6

2019-08-16	Remove meaningless comments in src/test	sd234678	-2/+0

2019-08-10	resolve: Remove remaining special cases from built-in macros	Vadim Petrochenkov	-5/+5

2019-07-15	pprust: Support `macro` macros	Vadim Petrochenkov	-0/+7

2019-07-15	pprust: Fix formatting regressions from the previous commits	Vadim Petrochenkov	-10/+57
	Fix some remaining cases of bad formatting Update some failing tests
2019-07-15	pprust: Do not convert attributes into `MetaItem`s for printing	Vadim Petrochenkov	-2/+9
	Fixes https://github.com/rust-lang/rust/issues/62628
2019-07-15	pprust: Use `print_mac_common` for delimited token groups	Vadim Petrochenkov	-3/+3

2019-07-15	pprust: Use `print_mac_common` for `macro_rules` definitions	Vadim Petrochenkov	-3/+5

2019-07-15	pprust: Move some methods to the `PrintState` trait	Vadim Petrochenkov	-2/+2
	So that path and macro argument printing code can be shared
2019-06-08	Introduce `#[rustc_dummy]` attribute and use it in tests	Vadim Petrochenkov	-155/+146
	Unlike other built-in attributes, this attribute accepts any input
2019-05-24	Move async/await tests to test/ui/async-await	varkor	-7/+0

2019-03-15	rustc: pass Option<&Substs> and Namespace around in ty::item_path.	Eduard-Mihai Burtescu	-17/+17

2019-03-14	Moved issue tests to subdirs and normalised names.	Alexander Regueiro	-6/+10

2019-03-03	Nit	Alexander Regueiro	-1/+1

2019-03-02	Fix C-variadic function printing	Dan Robertson	-0/+15
	There is no longer a need to append the string `", ..."` to a functions args as `...` is parsed as an argument and will appear in the functions arguments.
2019-01-26	Pretty print `$crate` as `crate` or `crate_name` in more cases	Vadim Petrochenkov	-0/+25

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

2018-12-19	Reintroduce special pretty-printing for `$crate` when it's necessary for ↵	Vadim Petrochenkov	-2/+2
	proc macros
2018-12-07	Various minor/cosmetic improvements to code	Alexander Regueiro	-1/+1

2018-11-30	tests: use `force-host` and `no-prefer-dynamic` in all proc_macro tests.	Eduard-Mihai Burtescu	-0/+1

2018-11-30	tests: remove ignore-stage1 where possible in proc_macro tests.	Eduard-Mihai Burtescu	-1/+0

2018-10-02	abolish ICE when pretty-printing async block	Zack M. Davis	-0/+7
	Joshua Netterfield reported an ICE when the unused-parentheses lint triggered around an async block (#54752). In order to compose an autofixable suggestion, the lint invokes the pretty-printer on the unnecessarily-parenthesized expression. (One wonders why the lint doesn't just use `SourceMap::span_to_snippet` instead, to preserve the formatting of the original source?—but for that, you'd have to ask the author of 5c9f806d.) But then the pretty-printer panics when trying to call `<pprust::State as PrintState>::end` when `State.boxes` is empty. Empirically, the problem would seem to be solved if we start some "boxes" beforehand in the `ast::ExprKind::Async` arm of the big match in `print_expr_outer_attr_style`, exactly like we do in the immediately-preceding match arm for `ast::ExprKind::Block`—it would seem pretty ("pretty") reasonable for the pretty-printing of async blocks to work a lot like the pretty-printing of ordinary non-async blocks, right?? Of course, it would be shamefully cargo-culty to commit code on the basis of this kind of mere reasoning-by-analogy (in contrast to understanding the design of the pretty-printer in such detail that the correctness of the patch is comprehended with all the lucid certainty of mathematical proof, rather than being merely surmised by intuition). But maybe we care more about fixing the bug with high probability today, than with certainty in some indefinite hypothetical future? Maybe the effort is worth a fifth of a shirt?? Humbly resolves #54752.
2018-09-10	update result of issue 12590 test	Tinco Andringa	-1/+1

2018-09-10	Fixed the test to match the compiler's output.	Felix S. Klock II	-6/+10

2018-09-10	Correctly close indentation blocks when pretty printing non-inline module	Tinco Andringa	-1/+2

2018-09-10	pretty=expanded should expand mod declarations	Tinco Andringa	-0/+42

2018-09-10	Track whether module declarations are inline (fixes #12590)	Tinco Andringa	-0/+31

2018-08-23	Stabilize 'attr_literals' feature.	Sergio Benitez	-1/+1

2018-08-14	syntax: gensym the injected std/core extern crates in the Rust 2018 edition.	Eduard-Mihai Burtescu	-2/+2

2018-08-06	Address review comments	Vadim Petrochenkov	-1/+1
	Adjust a few fulldeps and pretty-printing tests Fix rebase
2018-07-12	fix expected output of pretty/cast-lt and issue-4264 tests	Tinco Andringa	-4/+2

2018-04-03	Remove all unstable placement features	Aidan Hobson Sayers	-1/+0
	Closes #22181, #27779
2018-02-17	fix more typos found by codespell.	Matthias Krüger	-1/+1

2017-12-20	Fix whitespacing issues in pretty-printing of bounds	Vadim Petrochenkov	-4/+4

2017-12-12	Fix fallout in tests.	Jeffrey Seyfried	-1/+1

2017-11-07	Rollup merge of #45784 - harpocrates:fix/print-parens-cast-lt, r=kennytm	kennytm	-0/+46
	Pretty print parens around casts on the LHS of `<`/`<<` When pretty printing a cast expression occuring on the LHS of a `<` or `<<` expression, we should add parens around the cast. Otherwise, the `<`/`<<` gets interpreted as the beginning of the generics for the type on the RHS of the cast. Consider: $ cat parens_cast.rs macro_rules! negative { ($e:expr) => { $e < 0 } } fn main() { negative!(1 as i32); } Before this PR, the output of the following is not valid Rust: $ rustc -Z unstable-options --pretty=expanded parens_cast.rs #![feature(prelude_import)] #![no_std] #[prelude_import] use std::prelude::v1::; #[macro_use] extern crate std as std; macro_rules! negative(( $ e : expr ) => { $ e < 0 }); fn main() { 1 as i32 < 0; } After this PR, the output of the following is valid Rust: $ rustc -Z unstable-options --pretty=expanded parens_cast.rs #![feature(prelude_import)] #![no_std] #[prelude_import] use std::prelude::v1::; #[macro_use] extern crate std as std; macro_rules! negative(( $ e : expr ) => { $ e < 0 }); fn main() { (1 as i32) < 0; } I've gone through several README/wiki style documents but I'm still not sure where to test this though. I'm not even sure if this sort of thing is tested...
2017-11-06	Update comments in cast-lt.pp	Alec Theriault	-3/+1

2017-11-05	Fix comments	Alec Theriault	-3/+1

2017-11-05	Added tests	Alec Theriault	-0/+50

2017-11-03	Fix unsafe auto trait pretty print.	leonardo.yvens	-0/+2
	It was being printed wrong as auto unsafe trait
2017-11-03	Update pretty test for auto trait syntax.	leonardo.yvens	-3/+1

2017-10-08	Fix tests	Wonwoo Choi	-25/+25

2017-09-10	Use rvalue promotion to 'static instead of static items.	Eduard-Mihai Burtescu	-16/+6

2017-02-05	Update pretty test for derive attributes	Josh Driver	-51/+65
	Remove attr-variant-data.rs since it relies on quirks in legacy custom derive resolution (undefined derives only print a warning). Add a new test which uses a defined proc macro derive, and tests pretty printing of proc macro derive attributes.
2017-01-17	AST/HIR: Merge ObjectSum and PolyTraitRef	Vadim Petrochenkov	-3/+3

2016-12-22	Pretty-print `$crate::foo::bar` as `::foo::bar`.	Jeffrey Seyfried	-1/+1

2016-11-28	rustc: desugar UFCS as much as possible during HIR lowering.	Eduard Burtescu	-1/+1

2016-11-10	tests: fix fallout in pretty-printing output exact-match tests.	Eduard Burtescu	-66/+80