about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/errors.rs
diff options
context:
space:
mode:
authorest31 <MTest31@outlook.com>2023-02-24 04:38:45 +0100
committerest31 <MTest31@outlook.com>2023-02-24 05:12:03 +0100
commit28501166367ac12ac11fcf4bb06261e2c8139988 (patch)
tree8d09393e92fcac090c1badc212f6718569305bc0 /compiler/rustc_codegen_llvm/src/errors.rs
parent07c993eba8b76eae497e98433ae075b00f01be10 (diff)
downloadrust-28501166367ac12ac11fcf4bb06261e2c8139988.tar.gz
rust-28501166367ac12ac11fcf4bb06261e2c8139988.zip
Replace parse_[sth]_expr with parse_expr_[sth] function names
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.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions