about summary refs log tree commit diff
path: root/src/doc
diff options
context:
space:
mode:
authorChris Emerson <github@mail.nosreme.org>2019-10-12 23:11:52 +0100
committerSantiago Pastorino <spastorino@gmail.com>2019-10-12 19:11:52 -0300
commitc86863d441715b8b09bfecb392c24cee7944d28d (patch)
treef015a12f520e49cf2cfe0c5f82245bbdc385f787 /src/doc
parent1c14f496f17e19f0f62a77afc5ccee25ea0cc3d7 (diff)
downloadrust-c86863d441715b8b09bfecb392c24cee7944d28d.tar.gz
rust-c86863d441715b8b09bfecb392c24cee7944d28d.zip
Fix some paths: tt -> mbe (#465)
Diffstat (limited to 'src/doc')
-rw-r--r--src/doc/rustc-dev-guide/src/macro-expansion.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/doc/rustc-dev-guide/src/macro-expansion.md b/src/doc/rustc-dev-guide/src/macro-expansion.md
index f6a9b3b1f57..01a533ad6cf 100644
--- a/src/doc/rustc-dev-guide/src/macro-expansion.md
+++ b/src/doc/rustc-dev-guide/src/macro-expansion.md
@@ -7,7 +7,7 @@ before name resolution, macros are expanded using these portions of the code.
 The macro parser, in turn, may call the normal Rust parser when it needs to
 bind a metavariable (e.g.  `$my_expr`) while parsing the contents of a macro
 invocation. The code for macro expansion is in
-[`src/libsyntax/ext/tt/`][code_dir]. This chapter aims to explain how macro
+[`src/libsyntax/ext/mbe/`][code_dir]. This chapter aims to explain how macro
 expansion works.
 
 ### Example
@@ -61,7 +61,7 @@ invocations. Interestingly, both are done by the macro parser.
 Basically, the macro parser is like an NFA-based regex parser. It uses an
 algorithm similar in spirit to the [Earley parsing
 algorithm](https://en.wikipedia.org/wiki/Earley_parser). The macro parser is
-defined in [`src/libsyntax/ext/tt/macro_parser.rs`][code_mp].
+defined in [`src/libsyntax/ext/mbe/macro_parser.rs`][code_mp].
 
 The interface of the macro parser is as follows (this is slightly simplified):
 
@@ -110,7 +110,7 @@ normal Rust parser.
 As mentioned above, both definitions and invocations of macros are parsed using
 the macro parser. This is extremely non-intuitive and self-referential. The code
 to parse macro _definitions_ is in
-[`src/libsyntax/ext/tt/macro_rules.rs`][code_mr]. It defines the pattern for
+[`src/libsyntax/ext/mbe/macro_rules.rs`][code_mr]. It defines the pattern for
 matching for a macro definition as `$( $lhs:tt => $rhs:tt );+`. In other words,
 a `macro_rules` definition should have in its body at least one occurrence of a
 token tree followed by `=>` followed by another token tree. When the compiler
@@ -139,7 +139,7 @@ the parse is ambiguous, while if there are no matches at all, there is a syntax
 error.
 
 For more information about the macro parser's implementation, see the comments
-in [`src/libsyntax/ext/tt/macro_parser.rs`][code_mp].
+in [`src/libsyntax/ext/mbe/macro_parser.rs`][code_mp].
 
 ### Hygiene