about summary refs log tree commit diff
diff options
context:
space:
mode:
authorJoshua Nelson <jnelson@cloudflare.com>2022-05-05 20:11:41 -0500
committerJoshua Nelson <jnelson@cloudflare.com>2022-05-05 20:11:41 -0500
commit677b38c9185feab059d8c3ef3dffe49e67c26aba (patch)
treeea95a0f4e3785c8142d1a6a58ef4cc0eb9c39784
parent5dad51736ce13f8d8e41f2cfa83cc2c8e09b715b (diff)
downloadrust-677b38c9185feab059d8c3ef3dffe49e67c26aba.tar.gz
rust-677b38c9185feab059d8c3ef3dffe49e67c26aba.zip
Suggest -Zunpretty=ast-tree instead of -Zast-json
-Zast-json is being removed shortly: https://github.com/rust-lang/rust/pull/85993.
ast-tree does essentially the same thing, and still works today even before that PR lands.
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index fc663de8f79..022ba5d8414 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -67,7 +67,7 @@ and resolved paths.
 
 [`T-AST`] issues will generally need you to match against a predefined syntax structure.
 To figure out how this syntax structure is encoded in the AST, it is recommended to run
-`rustc -Z ast-json` on an example of the structure and compare with the [nodes in the AST docs].
+`rustc -Z unpretty=ast-tree` on an example of the structure and compare with the [nodes in the AST docs].
 Usually the lint will end up to be a nested series of matches and ifs, [like so][deep-nesting].
 But we can make it nest-less by using [if_chain] macro, [like this][nest-less].