rust/compiler/rustc_parse/src/parser/path.rs, branch 1.70.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.70.02023-04-10T22:19:46+00:00Remove `..` from return type notation2023-04-10T22:19:46+00:00Michael Gouletmichael@errs.io2023-04-10T22:16:17+00:00urn:sha1:24cbf81b8546beb8193217316acf4ded4117b4afAdd `(..)` syntax for RTN2023-03-28T01:14:28+00:00Michael Gouletmichael@errs.io2023-03-16T22:00:08+00:00urn:sha1:8b592db27afdc9edac084520bca98508da53c996RTN2023-03-28T01:02:15+00:00Michael Gouletmichael@errs.io2023-03-05T01:08:17+00:00urn:sha1:773e8a5ad1fa012bc1574c6733a700e094a48e3dReplace parse_[sth]_expr with parse_expr_[sth] function names2023-02-24T04:12:03+00:00est31MTest31@outlook.com2023-02-24T03:38:45+00:00urn:sha1:28501166367ac12ac11fcf4bb06261e2c8139988
This resolves an inconsistency in naming style for functions
on the parser, between functions parsing specific kinds of items
and those for expressions, favoring the parse_item_[sth] style
used by functions for items. There are multiple advantages
of that style:
* functions of both categories are collected in the same place
in the rustdoc output.
* it helps with autocompletion, as you can narrow down your
search for a function to those about expressions.
* it mirrors rust's path syntax where less specific things
come first, then it gets more specific, i.e.
std::collections::hash_map::Entry
The disadvantage is that it doesn't "read like a sentence"
any more, but I think the advantages weigh more greatly.
This change was mostly application of this command:
sed -i -E 's/(fn |\.)parse_([[:alnum:]_]+)_expr/\1parse_expr_\2/' compiler/rustc_parse/src/parser/*.rs
Plus very minor fixes outside of rustc_parse, and an invocation
of x fmt.
Use `ThinVec` in `ast::AngleBracketedArgs`.2023-02-21T00:51:56+00:00Nicholas Nethercoten.nethercote@gmail.com2023-01-30T03:37:06+00:00urn:sha1:1807027248f57d98a1490bfbe9eb3d3de944e60f`if $c:expr { Some($r:expr) } else { None }` =>> `$c.then(|| $r)`2023-02-16T15:26:00+00:00Maybe Wafflewaffle.lapkin@gmail.com2023-02-15T11:43:41+00:00urn:sha1:8751fa1a9abda9fc7ced6b03315efbd82310830drecover more unbraced const args2023-01-27T18:26:04+00:00León Orell Valerian Liehrme@fmease.dev2023-01-22T11:05:36+00:00urn:sha1:80a1536c7ab73c867d5a60f4441058e7e2231d8dclippy::complexity fixes2022-12-18T23:04:28+00:00Matthias Krügermatthias.krueger@famsik.de2022-12-18T11:45:56+00:00urn:sha1:1da4a499122f59201cf761b79f9e8c6ded1cb91d
filter_next
needless_question_mark
bind_instead_of_map
manual_find
derivable_impls
map_identity
redundant_slicing
skip_while_next
unnecessary_unwrap
needless_bool
Use `ThinVec` in `ast::Path`.2022-11-17T02:56:38+00:00Nicholas Nethercoten.nethercote@gmail.com2022-09-08T07:22:52+00:00urn:sha1:67d5cc0462f33773f042dc3c5ec9bd710095b1b4Box `ExprKind::{Closure,MethodCall}`, and `QSelf` in expressions, types, and patterns.2022-11-17T02:45:59+00:00Nicholas Nethercoten.nethercote@gmail.com2022-09-08T00:52:51+00:00urn:sha1:6b7ca2fcf2ebbba705f7a98c00bd56b5348ee9d7