aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Rudimentarily autocomplete tuple struct field accessrobojumper2019-04-062-0/+38
|
* Parse and infer tuple indicesrobojumper2019-04-0613-14/+210
|
* Merge #1115bors[bot]2019-04-051-0/+1
|\ | | | | | | | | | | | | | | 1115: Add .gitattributes for fix Windows Line-ending problem in `generated_grammar_is_fresh` r=matklad a=edwin0cheng Although https://github.com/rust-analyzer/rust-analyzer/issues/937 is marked as `Closed` . But it should work without setting `core.autocrlf` to `false` by this PR. Co-authored-by: Edwin Cheng <[email protected]>
| * add .gitattributesEdwin Cheng2019-04-051-0/+1
| |
* | Merge #1114bors[bot]2019-04-051-119/+119
|\ \ | |/ |/| | | | | | | | | | | 1114: Crate updates r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * Update depskjeremy2019-04-051-119/+119
| |
* | Merge #1112bors[bot]2019-04-055-7/+101
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 1112: Fix literal support in token tree to ast item list r=matklad a=edwin0cheng This PR implements following things : 1. Expose `next_token` from `ra_parse` 2. Fix the literal conversion in `token_tree_to_ast_item_list` 3. Add test for the conversion Co-authored-by: Edwin Cheng <[email protected]>
| * Add proper test for literals and fixed typo bugEdwin Cheng2019-04-053-5/+51
| |
| * Add classify_literal and undo expose next_tokenEdwin Cheng2019-04-055-8/+15
| |
| * Fix literal support in token tree to ast item listEdwin Cheng2019-04-054-4/+45
|/
* Merge #1111bors[bot]2019-04-053-20/+139
|\ | | | | | | | | | | | | | | | | | | | | 1111: Add multi-byte token support in token tree to ast item list r=matklad a=edwin0cheng As discusion in https://github.com/rust-analyzer/rust-analyzer/pull/1105 , this PR add implement all multi-byte tokens in `ra_mbe` crate. Co-authored-by: Edwin Cheng <[email protected]>
| * Clean upEdwin Cheng2019-04-041-29/+29
| |
| * Add multi-byte token support in tkn tree to astEdwin Cheng2019-04-043-20/+139
|/
* Merge #1108bors[bot]2019-04-041-1/+1
|\ | | | | | | | | | | | | | | 1108: Fix issue label link in docs/dev/README.md r=matklad a=pcpthm Co-authored-by: pcpthm <[email protected]>
| * Fix issue label link in docs/dev/README.mdpcpthm2019-04-041-1/+1
|/
* Merge #1107bors[bot]2019-04-041-4/+1
|\ | | | | | | | | | | | | | | 1107: Fix test fails when different target directory is used r=matklad a=pcpthm Co-authored-by: pcpthm <[email protected]>
| * Make robust about target directorypcpthm2019-04-041-4/+1
|/
* Merge #1106bors[bot]2019-04-042-7/+7
|\ | | | | | | | | | | | | | | 1106: :arrow_up: salsa r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * :arrow_up: salsaAleksey Kladov2019-04-042-7/+7
| |
* | Merge #1101bors[bot]2019-04-035-6/+95
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1101: Parse unsafe async / const unsafe fns properly r=matklad a=robojumper Also adds tests that `unsafe async fn` as well as `const unsafe fn` parse properly and that these keywords in the reversed order cause parse errors. [Playground link to verify that this is the correct order.](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=7850b8d92579de31c38f835f76afa4ce) Closes #1086. Co-authored-by: robojumper <[email protected]>
| * | Parse unsafe async / const unsafe fns properlyrobojumper2019-04-035-6/+95
| | |
* | | Merge #1098bors[bot]2019-04-031-1/+46
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 1098: added some docs to public functions r=matklad a=pasa some docs for #961 Co-authored-by: Sergey Parilin <[email protected]>
| * | added some docs to public functionsSergey Parilin2019-04-031-1/+46
| | |
* | | Merge #1068bors[bot]2019-04-0310-10/+193
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1068: profiling crate first draft r=matklad a=pasa I've made this first draft for #961 Could you look at it? Is this something what you are looking for? It has lack of tests. I can't figure out how to test stderr output in rust right now. Do you have some clues? Additionally I'm thinking about to implement procedural macros to annotate methods with this profiler. Will it be helpful? Co-authored-by: Sergey Parilin <[email protected]>
| * | Merge remote-tracking branch 'upstream/master' into issue961_profilingSergey Parilin2019-04-0254-1180/+1943
| |\ \
| * | | PR issuse resolvedSergey Parilin2019-04-029-10/+30
| | | |
| * | | some PR issues fixedSergey Parilin2019-03-291-82/+68
| | | |
| * | | profiling crate first draftSergey Parilin2019-03-273-0/+177
| | | |
* | | | Merge #1097bors[bot]2019-04-031-2/+5
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1097: Fix VSCode cargo-watch functionality on Linux. r=matklad a=kiljacken As of #1079 the VSCode cargo-watch functionality has been broken on Linux systems. The cause seems to be that linux takes the added quotes inside process arguments literally, so it attempts to make cargo-watch run the command `cargo "check --message-format json"` with the entire quoted part being treated as a single long subcommand, which cargo doesn't know how to handle. Removing the extra quotes solves the issue. Closes #1096 Co-authored-by: Emil Lauridsen <[email protected]>
| * | | | Fix eslint errorsEmil Lauridsen2019-04-031-1/+1
| | | | |
| * | | | Add extra double quotes only on Windows.Emil Lauridsen2019-04-031-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As tested by @edwin0cheng, Windows requires the quotes removed in the previous commit. This commit re-adds the quotes gated by an if statement on the node environment, so that quotes are only added on Windows.
| * | | | Fix VSCode cargo-watch functionality on Linux.Emil Lauridsen2019-04-031-2/+1
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As of #1079 the VSCode cargo-watch functionality has been broken on Linux systems. The cause seems to be that linux takes the added quotes inside process arguments literally, so it attempts to make cargo-watch run the command `cargo "check --message-format json"` with the entire quoted part being treated as a single long subcommand, which cargo doesn't know how to handle. Removing the extra quotes solves the issue.
* | | | Merge #1076bors[bot]2019-04-0210-49/+231
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1076: Const body inference r=flodiebold a=Lapz This is the second part of #887. I've added type inference on const bodies and introduced the DefWithBody containing Function, Const and Static. I want to add tests but im unsure on how I would go about testing that completions work. Co-authored-by: Lenard Pratt <[email protected]>
| * | | | made ExprCollector pub(crate) and movedLenard Pratt2019-04-022-14/+11
| | | | | | | | | | | | | | | | | | | | collect_fn_body_syntax
| * | | | Added const bodies and static body to the astLenard Pratt2019-04-0210-91/+180
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and added inference the inference test reduce code duplication
| * | | | Added defWithBodyLenard Pratt2019-03-307-24/+120
| | | | |
* | | | | Merge #1094bors[bot]2019-04-022-44/+78
|\ \ \ \ \ | |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1094: Improve cargo-watch animation and refactoring r=matklad a=edwin0cheng * Refactoring code and fixed some minor bugs. * Add more error log and better error handling. * Add current checking artifact name in Cargo-watch animation. ![new_status_animation](https://i.imgur.com/Zr2JLa5.gif) Co-authored-by: Edwin Cheng <[email protected]>
| * | | | Add cargo-watch package animation and refactoringEdwin Cheng2019-04-022-44/+78
|/ / / /
* | | | Merge #1093bors[bot]2019-04-027-400/+336
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1093: simplify r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | simplifyAleksey Kladov2019-04-027-400/+336
| | | | |
* | | | | Merge #1092bors[bot]2019-04-026-29/+70
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1092: always produce source for import r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | always produce source for importAleksey Kladov2019-04-026-29/+70
|/ / / /
* | | | Merge #1090bors[bot]2019-04-02221-8921/+8921
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1090: always show token text r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | always show token textAleksey Kladov2019-04-02221-8921/+8921
| | | | |
* | | | | Merge #1091bors[bot]2019-04-021-1/+1
|\ \ \ \ \ | |/ / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1091: fix inner block doc comments r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | fix inner block doc commentsAleksey Kladov2019-04-021-1/+1
|/ / / /
* | | | Merge #1089bors[bot]2019-04-025-23/+26
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1089: fix a panic with glob-import missing a source map r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | | | fix a panic with glob-import missing a source mapAleksey Kladov2019-04-025-23/+26
| | | | |
* | | | | Merge #1079bors[bot]2019-04-0211-44/+448
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1079: Improve cargo-watch usage in vscode plugin r=matklad a=edwin0cheng *This PR try to improve current cargo-watch usage in VSCode :* 1. Add Multi-lines error support : ![multilines-error](https://i.imgur.com/gbLEwMG.gif) 2. Add cargo-watch status animation : ![cargo-watch-status](https://i.imgur.com/GbHwzjj.gif) *Implementation Details* * Current VSCode `ProblemMatcher` still do not support multiple line parsing. * However we can, spawn a cargo watch process instead of using vscode.Task to allow more control. * Use `cargo-check --message-format json` to get json format of compiler-message. * Use `vscode.DiagnosticCollection` to manage the problems directly, which allow multiple lines diagnostic. However, * VSCode use non mono-space font for problems, at this moment i cannot find a good solution about it. * I am not so good in typescript, please let me know if anything is bad in this PR. Co-authored-by: Edwin Cheng <[email protected]> Co-authored-by: Edwin Cheng <[email protected]>
| * | | | | Fix prettier errorEdwin Cheng2019-04-021-1/+1
| | | | | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 03:08:33 +0000