Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2024-11-17 02:08:30 +00:00
Code Issues Projects Releases Packages Wiki Activity

Merge #4837

Browse source 
4837: Fix parser test directory name in dev docs r=matklad a=jacg

The docs referred to `parser/error` while in reality it is `parser/err`.

Co-authored-by: Jacek Generowicz <jacg@my-post-office.net>
This commit is contained in:
bors[bot] 2020-06-10 19:29:04 +00:00 committed by GitHub
commit dfbd81e84a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/dev/README.md
View file

@ -308,7 +308,7 @@ The results are 100% Rust specific though.
Test for parser (`ra_parser`) live in `ra_syntax` crate (see `test_data` direcotory). Test for parser (`ra_parser`) live in `ra_syntax` crate (see `test_data` direcotory).
There are two kinds of tests: There are two kinds of tests:
* Manually written test cases in `parser/ok` and `parser/error` * Manually written test cases in `parser/ok` and `parser/err`
* "Inline" tests in `parser/inline` (these are generated) from comments in `ra_parser` crate. * "Inline" tests in `parser/inline` (these are generated) from comments in `ra_parser` crate.
The 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. The 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.