aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2020-06-15 10:02:53 +0100
committerGitHub <[email protected]>2020-06-15 10:02:53 +0100
commitdb6100dbaa4f09543c7e6f2ab9986daa55919ad5 (patch)
tree165cdcd914e8f201fb44e4ab7e5c04cf72994195 /docs
parent672d160b013df82b1729fd3db130ff7b6f9b5b31 (diff)
parentb5c4f2faa2a39bad9af35e7d90e9ed6151a6a0d5 (diff)
Merge #4889
4889: Deprecate hir::Path::from_ast r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
Diffstat (limited to 'docs')
-rw-r--r--docs/dev/README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md
index 2e4a45998..4cb5dfaa0 100644
--- a/docs/dev/README.md
+++ b/docs/dev/README.md
@@ -342,6 +342,12 @@ There are two kinds of tests:
342The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for. 342The purpose of inline tests is not to achieve full coverage by test cases, but to explain to the reader of the code what each particular `if` and `match` is responsible for.
343If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test. 343If you are tempted to add a large inline test, it might be a good idea to leave only the simplest example in place, and move the test to a manual `parser/ok` test.
344 344
345To update test data, run with `UPDATE_EXPECTATIONS` variable:
346
347```bash
348env UPDATE_EXPECTATIONS=1 cargo qt
349```
350
345# Logging 351# Logging
346 352
347Logging is done by both rust-analyzer and VS Code, so it might be tricky to 353Logging is done by both rust-analyzer and VS Code, so it might be tricky to