aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 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
| * Remove uneeded charactersDJMcNab2018-12-081-3/+3
| |
| * Improve the extend keybinding to not conflictDJMcNab2018-12-081-1/+1
| |
* | Merge #266bors[bot]2018-12-081-3/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | 266: handle expanding of words in comments at the beginning or end of line r=matklad a=vemoo After fixing #140 i realized that the logic to determine word boundaries was not correct. It would only consider a word something surrounded by whitespaces in the line, but not newlines before and after the line. This means that one of the tests has changed, but i think that's what was intended. Co-authored-by: Bernardo <[email protected]>
| * | find next whitespace or begining or endBernardo2018-12-081-3/+3
|/ /
* | Merge #265bors[bot]2018-12-084-24/+59
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 265: Refactor symbol resolve API r=matklad a=matklad Introduce ReferenceResolution to avoid nesting to many non-nominal types. Co-authored-by: Aleksey Kladov <[email protected]>
| * | Refactor symbol resolve APIAleksey Kladov2018-12-084-24/+59
| | | | | | | | | | | | | | | Introduce ReferenceResolution to avoid nesting to many non-nominal types.
* | | Merge #263bors[bot]2018-12-0817-22/+28
|\| | | | | | | | | | | | | | | | | | | | | | | 263: New modules r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | account for new layout when collecting testsAleksey Kladov2018-12-081-2/+8
| | |
| * | grand module renameAleksey Kladov2018-12-0815-0/+0
| | |
| * | resolve 2018 style modulesAleksey Kladov2018-12-081-20/+20
| | |
* | | Merge #264bors[bot]2018-12-081-1/+20
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 264: check for empty range when extending in comment r=matklad a=vemoo fix for #140 Co-authored-by: Bernardo <[email protected]>
| * | check for empty range when extending in commentBernardo2018-12-081-1/+20
| |/
* | reformatAleksey Kladov2018-12-082-2/+3
| |
* | Add a better text for hover and stop duplicating work done in ↵DJMcNab2018-12-087-30/+98
| | | | | | | | approximatelly_resolve_symbol
* | Fix typo in commentDJMcNab2018-12-081-10/+15
| |
* | Clarify and correct comment about multi_byte_tokensDJMcNab2018-12-081-2/+2
| |
* | Fix the range of a hover request to be more in line with prior artDJMcNab2018-12-081-1/+8
|/
* Merge #261bors[bot]2018-12-066-19/+177
|\ | | | | | | | | | | | | | | 261: Add heavy test for code actions r=matklad a=flodiebold Here's the test for the code actions; I didn't find anything fitting on crates.io ([assert-json-diff](https://crates.io/crates/assert-json-diff) looks kind of nice, but doesn't have anything like the wildcards), so I copied the cargo code as you suggested. Co-authored-by: Florian Diebold <[email protected]>
| * Add test for code actionsFlorian Diebold2018-12-061-1/+60
| |
| * Use json comparison code from cargo for heavy testsFlorian Diebold2018-12-066-18/+117
|/
* Merge #260bors[bot]2018-12-0627-180/+82
|\ | | | | | | | | | | | | | | 260: Modernize r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * modernize even moreAleksey Kladov2018-12-0612-70/+29
| |
| * modernize moreAleksey Kladov2018-12-0610-56/+42
| |
| * drop extern cratesAleksey Kladov2018-12-063-26/+0
| |
| * modernize some filesAleksey Kladov2018-12-063-10/+4
| |
| * modernize some codeAleksey Kladov2018-12-063-18/+7
| |
* | Merge #259bors[bot]2018-12-061-1/+1
|\ \ | |/ |/| | | | | | | | | | | 259: dedupe testing & formatting toolchains r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * dedupe testing & formatting toolchainsAleksey Kladov2018-12-061-1/+1
|/
* Merge #256bors[bot]2018-12-0611-1/+467
|\ | | | | | | | | | | | | | | 256: Improve/add use_item documentation r=matklad a=DJMcNab Adds some documentation to use_item explaining all code paths (use imports are hard, especially with the ongoing discussion of anchored v. uniform paths - see https://github.com/rust-lang/rust/issues/55618 for what appears to be the latest developments) Co-authored-by: DJMcNab <[email protected]>
| * Update use path testDJMcNab2018-12-052-74/+2
| |
| * Improve/add the use_item documentationDJMcNab2018-12-0511-1/+539
| |
* | Merge #258bors[bot]2018-12-062-2/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | 258: :arrow_up: 1.31.0 :tada: r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | :arrow_up: 1.31.0 :tada:Aleksey Kladov2018-12-062-2/+2
|/ /
* | Merge #253bors[bot]2018-12-051-2/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 253: Fix diagnostic fixes showing up everywhere r=matklad a=flodiebold The LSP code action request always returned the fixes for all diagnostics anywhere in the file, because of a shadowed variable. There's no test yet; I wasn't sure where to add it. I tried adding one in `heavy_tests`, but that's a bit uncomfortable because the code action response contains the (random) file paths. I could make it work, but wanted to ask beforehand what you think. Co-authored-by: Florian Diebold <[email protected]>
| * | Fix diagnostic fixes showing up everywhereFlorian Diebold2018-12-021-2/+2
| | | | | | | | | | | | | | | The LSP code action request always returned the fixes for all diagnostics anywhere in the file, because of a shadowed variable.
* | | Merge #257bors[bot]2018-12-051-1/+1
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | 257: Fix a copy and pasting typo in lexer/ptr.rs r=matklad a=DJMcNab Co-authored-by: DJMcNab <[email protected]>
| * | Fix a copy and pasting typoDJMcNab2018-12-051-1/+1
|/ /
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-27 05:02:51 +0000