| common |
|
|
| debug |
|
|
| macros |
|
|
| regression |
|
|
| regression.rs |
|
132 |
| repo |
|
|
| test_asyncness.rs |
|
806 |
| test_attribute.rs |
|
4429 |
| test_derive_input.rs |
|
21846 |
| test_expr.rs |
|
13923 |
| test_generics.rs |
|
9073 |
| test_grouping.rs |
|
1518 |
| test_ident.rs |
|
1288 |
| test_item.rs |
|
8102 |
| test_iterators.rs |
|
1774 |
| test_lit.rs |
|
8512 |
| test_meta.rs |
|
3152 |
| test_parse_buffer.rs |
|
2707 |
| test_parse_quote.rs |
|
3530 |
| test_parse_stream.rs |
|
316 |
| test_pat.rs |
|
4510 |
| test_path.rs |
|
3756 |
| test_precedence.rs |
This test does the following for every file in the rust-lang/rust repo:
1. Parse the file using syn into a syn::File.
2. Extract every syn::Expr from the file.
3. Print each expr to a string of source code.
4. Parse the source code using librustc_parse into a rustc_ast::Expr.
5. For both the syn::Expr and rustc_ast::Expr, crawl the syntax tree to
insert parentheses surrounding every subexpression.
6. Serialize the fully parenthesized syn::Expr to a string of source code.
7. Parse the fully parenthesized source code using librustc_parse.
8. Compare the rustc_ast::Expr resulting from parenthesizing using rustc
data structures vs syn data structures, ignoring spans. If they agree,
rustc's parser and syn's parser have identical handling of expression
precedence. |
18133 |
| test_receiver.rs |
|
8290 |
| test_round_trip.rs |
|
8150 |
| test_shebang.rs |
|
1757 |
| test_should_parse.rs |
|
915 |
| test_size.rs |
|
780 |
| test_stmt.rs |
|
8387 |
| test_token_trees.rs |
|
675 |
| test_ty.rs |
|
12358 |
| test_visibility.rs |
|
3704 |
| zzz_stable.rs |
|
1098 |