aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Prepare gen_lsp_server for publishingAleksey Kladov2018-10-094-17/+88
|
* Merge #104bors[bot]2018-10-0925-494/+805
|\ | | | | | | | | | | | | | | | | | | | | | | 104: Add vscode extension to CI r=aochagavia a=DJMcNab Note that this testing is only done on travis - we are only running formatting and linting, so feature parity on appveyor is not required. CC @aochagavia. Fixes? #100 Co-authored-by: Daniel McNab <[email protected]>
| * Run prettier on all filesDaniel McNab2018-10-0823-129/+220
| |
| * Add tslint and prettier to ciDaniel McNab2018-10-085-403/+623
|/
* Merge #103bors[bot]2018-10-0818-415/+557
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 103: WIP: refactor vscode extension r=aochagavia a=aochagavia Todo: - [x] Add more comments, so other people can find their way in the codebase - [x] Resolve remaining tslint suggestions - [ ] Integrate with CI @matklad The standard configuration of tslint forbids using `console.log` and `console.error`. Is there any reason we are using those or can I remove them? If they are used for debugging purposes I would prefer to remove them and rely on vscode's excellent debugger. Co-authored-by: Adolfo Ochagavía <[email protected]>
| * Add some commentsAdolfo Ochagavía2018-10-084-25/+44
| |
| * Fix remaining tslint suggestionsAdolfo Ochagavía2018-10-0815-78/+82
| |
| * Apply tslint suggestions, round oneAdolfo Ochagavía2018-10-0716-242/+258
| |
| * Refactor vscode extensionAdolfo Ochagavía2018-10-0714-415/+518
| |
* | Attach comments smartlyAleksey Kladov2018-10-084-24/+97
| |
* | replace loop with iteratorsAleksey Kladov2018-10-081-6/+7
| |
* | Simplify event processingAleksey Kladov2018-10-086-98/+122
| |
* | tfn snippetAleksey Kladov2018-10-081-0/+32
|/
* Merge #98bors[bot]2018-10-074-7/+97
|\ | | | | | | | | | | | | | | 98: WIP: Add resolve_local_name to resolve names in a function scope r=kjeremy a=kjeremy First step to resolving #80 Co-authored-by: Jeremy A. Kolb <[email protected]>
| * Remove functional noopJeremy A. Kolb2018-10-061-8/+0
| |
| * Resolve local names firstJeremy A. Kolb2018-10-063-15/+14
| |
| * WIP: This doesn't currently work but I also don't think it's the right ↵Jeremy A. Kolb2018-10-053-3/+25
| | | | | | | | abstraction
| * Add resolve_local_name to resolve names in a function scopeJeremy A. Kolb2018-10-051-2/+79
| |
* | Merge #96bors[bot]2018-10-077-35/+75
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 96: [WIP] Begin to add some contributing docs (#95) r=matklad a=DJMcNab Currently adds some documentation about `cargo gen-kinds`. Note that I am unsure of some of the details, such as why `DOT` is in `multi_byte_tokens`, hence the [WIP] tag. Based on #95. Co-authored-by: Daniel McNab <[email protected]>
| * | Reformat CONTRIBUTING.mdDaniel McNab2018-10-041-45/+46
| | | | | | | | | | | | | | | This uses: `prettier --prose-wrap always ./CONTRIBUTING.md --write`
| * | Add `cargo gen-kinds` documentationDaniel McNab2018-10-047-4/+43
| |/
* | Merge #99bors[bot]2018-10-072-12/+37
|\ \ | |/ |/| | | | | | | | | | | 99: Dynamically apply highlightingOn config r=matklad a=aochagavia Fixes #84 Co-authored-by: Adolfo Ochagavía <[email protected]>
| * Dynamically apply highlightingOn configAdolfo Ochagavía2018-10-062-12/+37
|/ | | | Fixes #84
* Merge #94bors[bot]2018-10-041-4/+32
|\ | | | | | | | | | | | | | | 94: Extend comments by single word first r=matklad a=kjeremy Fixes #88 Co-authored-by: Jeremy A. Kolb <[email protected]>
| * Pull casts out of TextUnitJeremy A. Kolb2018-10-041-4/+4
| |
| * Simplify extend_single_word_in_commentJeremy A. Kolb2018-10-041-15/+11
| |
| * Extend comments by single word firstJeremy A. Kolb2018-10-031-4/+36
| | | | | | | | Fixes #88
* | Merge #93bors[bot]2018-10-043-12/+59
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 93: Support leading pipe in match arms r=matklad a=DJMcNab This adds support for match arms of the form: ```rust <...> | X | Y => <...>, | X => <...>, | 1..2 => <...>, etc ``` # Implementation discussion This just naïvely 'eats' a leading pipe if one is available. The equivalent line in the reference `libsyntax` is in [`parse_arm`](https://github.com/rust-lang/rust/blob/441519536c8bd138e8c651743249acd6814747a1/src/libsyntax/parse/parser.rs#L3552). As noted in the comment linked above, this feature was formally introduced as a result of rust-lang/rfcs#1925. This feature is in active use in the [`rust-analyzer` codebase](https://github.com/matklad/rust-analyzer/blob/c87fcb4ea5874a7307c1d9d1192e923f3ae2c922/crates/ra_syntax/src/syntax_kinds/generated.rs#L231) I have added some tests for this feature, but maybe more would be required EDIT: Always looking for feedback - is this PR description over-engineered? Co-authored-by: Daniel McNab <[email protected]>
| * Support leading pipe in match armsDaniel McNab2018-10-033-12/+59
| |
* | Merge #92bors[bot]2018-10-021-22/+22
|\ \ | | | | | | | | | | | | | | | | | | | | | 92: cargo update r=matklad a=kjeremy Co-authored-by: Jeremy A. Kolb <[email protected]>
| * | cargo updateJeremy A. Kolb2018-10-021-22/+22
|/ /
* | Merge pull request #91 from kjeremy/ignore-ideaAleksey Kladov2018-10-021-0/+1
|\ \ | | | | | | Ignore .idea/
| * | Ignore .idea/Jeremy A. Kolb2018-10-021-0/+1
|/ /
* | Merge #90bors[bot]2018-10-0215-80/+70
|\ \ | | | | | | | | | | | | | | | | | | | | | 90: Inherent traversal r=matklad a=matklad bors r+ Co-authored-by: Aleksey Kladov <[email protected]>
| * | Make siblings an inherent methodAleksey Kladov2018-10-026-34/+30
| | |
| * | make ancestors and descendants inherentAleksey Kladov2018-10-0214-46/+40
| | |
| * | use aliasesAleksey Kladov2018-10-021-2/+2
|/ /
* | Merge #85bors[bot]2018-10-0213-532/+150
|\ \ | |/ |/| | | | | | | | | | | 85: start moving syntax tree to a separate crate r=matklad a=matklad WIP Co-authored-by: Aleksey Kladov <[email protected]>
| * Move to rowan for syntax tree implAleksey Kladov2018-10-0213-532/+150
|/
* Merge #83bors[bot]2018-09-292-4/+23
|\ | | | | | | | | | | | | | | 83: Add a setting to disable custom syntax highlighting r=matklad a=aochagavia Co-authored-by: Adolfo Ochagavía <[email protected]>
| * Add a setting to disable custom syntax highlightingAdolfo Ochagavía2018-09-292-4/+23
| |
* | fix code actionsAleksey Kladov2018-09-291-1/+1
|/
* support 2018 pathsAleksey Kladov2018-09-293-3/+21
|
* Merge #81bors[bot]2018-09-265-2/+148
|\ | | | | | | | | | | | | | | 81: [WIP] Reject impl keyword inside impl header r=matklad a=csmoe Closes #77 Co-authored-by: csmoe <[email protected]>
| * generate testsuite for impl_typecsmoe2018-09-265-13/+94
| |
| * parse impl typecsmoe2018-09-253-57/+44
| |
| * reject impl keyword in impl headercsmoe2018-09-241-2/+10
| |
| * add test for impl recoverycsmoe2018-09-242-0/+70
| |
* | Merge #79bors[bot]2018-09-259-48/+236
|\ \ | |/ |/| | | | | | | | | | | | | | | 79: Implement Folding Ranges r=matklad a=kjeremy Implements folding ranges for comments and imports. Bumps LSP to 3.13 Co-authored-by: Jeremy A. Kolb <[email protected]>
| * Unit TestsJeremy A. Kolb2018-09-241-0/+56
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-18 02:01:24 +0000