aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Gc syntax trees after every modificationAleksey Kladov2018-12-182-8/+17
|/ /
* | Work around a bugAleksey Kladov2018-12-181-4/+7
| | | | | | | | cc #288
* | Merge #286bors[bot]2018-12-189-46/+62
|\ \ | | | | | | | | | | | | | | | | | | | | | 286: move thread worker to a separate crate r=matklad a=matklad Going to tackle https://github.com/rust-analyzer/rust-analyzer/issues/243, this is a refactoring towards that goal Co-authored-by: Aleksey Kladov <[email protected]>
| * | move thread worker to a separate crateAleksey Kladov2018-12-189-46/+62
|/ /
* | Merge #284bors[bot]2018-12-181-5/+5
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 284: By default, log only to stderr, and not to disk. r=matklad a=eminence This fixes a common problem when running under VS Code, the user doesn't have permissions to create a `log` directory in the CWD. The old behavior can be re-enabled by setting `RA_INTERNAL_MODE=1` Fixes #282 Co-authored-by: Andrew Chin <[email protected]>
| * By default, log only to stderr, and not to disk.Andrew Chin2018-12-171-5/+5
| | | | | | | | | | | | | | This fixes a common problem when running under VS Code, the user doesn't have permissions to create a `log` directory in the CWD. The old behavior can be re-enabled by setting RA_INTERNAL_MODE=1
* | Merge #283bors[bot]2018-12-171-18/+58
|\ \ | |/ |/| | | | | | | | | | | 283: Docs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * big pictureAleksey Kladov2018-12-171-1/+28
| |
| * docs about cancelationAleksey Kladov2018-12-171-0/+5
| |
| * update architecture.mdAleksey Kladov2018-12-171-19/+27
|/
* Merge #280bors[bot]2018-12-174-15/+66
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 280: Fixed cast expression parsing in ra_syntax. r=matklad a=ruabmbua Fixes #279 Related to https://github.com/rust-analyzer/rust-analyzer/pull/273 The cast expression expected any type via types::type_() function, but the language spec does only allow TypeNoBounds (types without direct extra bounds via `+`). **Example:** ```rust fn test() { 6i8 as i32 + 5; } ``` This fails, because the types::type_() function which should parse the type after the as keyword is greedy, and takes the plus sign after path types as extra type bounds. My proposed fix is to replace the not implemented `type_no_plus()` just calls (`type_()`) function, which is used at several places. The replacement is `type_with_bounds_cond(p: &mut Parser, allow_bounds: bool)`, which passes the condition to relevant sub-parsers. This function is then called by `type_()` and the new public `type_no_bounds()`. Co-authored-by: Roland Ruckerbauer <[email protected]>
| * Fixed cast expression parsing in ra_syntax.Roland Ruckerbauer2018-12-174-15/+66
|/ | | | | | | | | | | | | | | | | | | | | | The cast expression expected any type via types::type_() function, but the language spec does only allow TypeNoBounds (types without direct extra bounds via `+`). **Example:** ```rust fn test() { 6i8 as i32 + 5; } ``` This fails, because the types::type_() function which should parse the type after the as keyword is greedy, and takes all plus sign after path types as extra. My proposed fix is to replace the not implemented `type_no_plus()` just calls (`type_()`) function, which is used at several places. The replacement is `type_with_bounds_cond(p: &mut Parser, allow_bounds: bool)`, which passes the condition to relevant sub-parsers. This function is then called by `type_()` and the new public `type_no_bounds()`.
* fix installation on windowsAleksey Kladov2018-12-171-1/+2
|
* Merge #277bors[bot]2018-12-153-15/+15
|\ | | | | | | | | | | | | | | 277: use new clear-terminal feature r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * use new clear-terminal featureAleksey Kladov2018-12-153-15/+15
|/
* Merge #276bors[bot]2018-12-1221-110/+156
|\ | | | | | | | | | | | | | | | | | | 276: Extract and rename AtomEdit and Edit into ra_text_edit r=matklad a=vemoo As discused in #105 Co-authored-by: Bernardo <[email protected]>
| * rename Edit to TextEdit and AtomEdit to AtomTextEditBernardo2018-12-1111-87/+92
| |
| * extract AtomEdit and Edit into new ra_text_edit crateBernardo2018-12-1019-40/+81
|/
* Merge #275bors[bot]2018-12-101-8/+18
|\ | | | | | | | | | | | | | | 275: Update ARCHITECTURE.md r=matklad a=h-michael I am still not familiar with the code base, so mostly I quote crate's comments. Co-authored-by: Hirokazu Hata <[email protected]>
| * Update ARCHITECTURE.mdHirokazu Hata2018-12-101-8/+18
|/
* Merge #274bors[bot]2018-12-101-0/+1
|\ | | | | | | | | | | | | | | | | 274: Add crates/*/target to gitignore r=matklad a=h-michael I am using rls and rust-analyzer together. Rls creates cache in `crates/*/target`, so I would like to add it to gitignore as well. Co-authored-by: Hirokazu Hata <[email protected]>
| * Add crates/*/target to gitignoreHirokazu Hata2018-12-101-0/+1
|/
* Merge #272bors[bot]2018-12-091-2/+30
|\ | | | | | | | | | | | | | | 272: use \b as word boundary when expanding single word in comments r=matklad a=vemoo as discused in #266 Co-authored-by: Bernardo <[email protected]>
| * use \b as word boundaryBernardo2018-12-091-2/+30
|/
* Merge #271bors[bot]2018-12-095-15/+75
|\ | | | | | | | | | | | | | | | | | | 271: Implement format hook r=matklad a=DJMcNab Tentatively: fixes #155. However, this does add all changes in staged files, which might not be desirable. However, I think we can't solve that without explicit support in rustfmt for it, so it should be fine. Co-authored-by: DJMcNab <[email protected]>
| * Reimplement format-hook using a rust binaryDJMcNab2018-12-093-27/+52
| |
| * Fix alignment of `.cargo/config`DJMcNab2018-12-091-5/+5
| |
| * Update hook to not add unstaged filesDJMcNab2018-12-091-1/+3
| |
| * Implement and test format hookDJMcNab2018-12-094-8/+41
| |
* | Answer canceled requestsAleksey Kladov2018-12-091-1/+8
| |
* | verbose assertions in SourceFileItemsAleksey Kladov2018-12-091-6/+15
| |
* | Merge #268bors[bot]2018-12-0912-169/+373
|\ \ | | | | | | | | | | | | | | | | | | | | | 268: WIP: resolve imports across crates r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | resolve extern crates propertlyAleksey Kladov2018-12-094-51/+98
| | |
| * | move tests to separate fileAleksey Kladov2018-12-092-97/+95
| | |
| * | WIP: resolve across cratesAleksey Kladov2018-12-091-14/+41
| | |
| * | make resolver fields privateAleksey Kladov2018-12-092-12/+22
| | |
| * | return dependencies with namesAleksey Kladov2018-12-092-6/+17
| | |
| * | thread info about dep namesAleksey Kladov2018-12-093-12/+24
| | |
| * | more crate boilerplateAleksey Kladov2018-12-095-13/+54
| | |
| * | hir::Crate boilerplateAleksey Kladov2018-12-092-2/+21
| | |
| * | propagate deps to CrateGraphAleksey Kladov2018-12-093-14/+43
| | |
| * | track deps in project modelAleksey Kladov2018-12-091-0/+10
|/ /
* | remove direct dep on event-stream: malisious version was unpublishedAleksey Kladov2018-12-092-126/+39
| |
* | Merge #270bors[bot]2018-12-098-16/+40
|\ \ | |/ |/| | | | | | | | | | | 270: Checks r=matklad a=matklad I see occasional panics when binding sources. Hopefully this assertions will make it clear where do the panics come from/ Co-authored-by: Aleksey Kladov <[email protected]>
| * Check Fileid in SourceFileMapAleksey Kladov2018-12-095-7/+23
| |
| * switch threadpool back from rayon to threadpoolAleksey Kladov2018-12-093-9/+17
|/ | | | | rayon does not replenish the pool when the thread panics, but we must be reselient to bugs.
* Merge #267bors[bot]2018-12-095-733/+807
|\ | | | | | | | | | | | | | | 267: Fix the extend keybinding r=DJMcNab a=DJMcNab Make the extend selection keybinding less annoying for users not used to Injelli-J (myself included). Also fixes a minor style issue and runs `npm update`. Co-authored-by: DJMcNab <[email protected]>
| * Fix cargo format component name and run rustfmtDJMcNab2018-12-092-8/+2
| |
| * Add package command and upgrade event-streamDJMcNab2018-12-083-5/+21
| |
| * Run npm update and add private and preview flagsDJMcNab2018-12-082-721/+785
| | | | | | | | | | | | | | | | Private stops npm publish working, which would be nonsensical anyway In case it gets added to the vscode extension repository, preview marks it as such Private may also prevent publishing to the vscode extension repository
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 04:30:20 +0000