diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2020-03-16 13:16:44 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-16 13:16:44 +0100 |
| commit | 8872d9057230e46f4bf35af5880cc6095a06e744 (patch) | |
| tree | 66780180c8104b7528546896aa9e7ebec9ce6333 /src/test/rustdoc-ui/coverage/json.rs | |
| parent | 8f2482b8012993a7e173f2296880818c1b90a0ca (diff) | |
| parent | db638bd123b7b73be691f7b4daebb61469587a27 (diff) | |
| download | rust-8872d9057230e46f4bf35af5880cc6095a06e744.tar.gz rust-8872d9057230e46f4bf35af5880cc6095a06e744.zip | |
Rollup merge of #69989 - petrochenkov:nolegacy, r=eddyb,matthewjasper
resolve/hygiene: `macro_rules` are not "legacy" The "modern" vs "legacy" naming was introduced by jseyfried during initial implementation of macros 2.0. At this point it's clear that `macro_rules` are not going anywhere and won't be deprecated in the near future. So this PR changes the naming "legacy" (when it implies "macro_rules") to "macro_rules". This should also help people reading this code because it's wasn't obvious that "legacy" actually meant "macro_rules" in these contexts. The most contentious renaming here is probably ``` fn modern -> fn normalize_to_macros_2_0 fn modern_and_legacy -> fn normalize_to_macro_rules ``` Other alternatives that I could think of are `normalize_to_opaque`/`normalize_to_semitransparent`, or `strip_non_opaque`/`strip_transparent`, but they seemed less intuitive. The documentation to these functions can be found in `symbol.rs`. r? @matthewjasper
Diffstat (limited to 'src/test/rustdoc-ui/coverage/json.rs')
0 files changed, 0 insertions, 0 deletions