aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | | add error handling to fetchArtifactReleaseInfo(), throw Error when no ↵Veetaha2020-02-241-19/+37
| |/ / | | | | | | | | | artifact found
* | | Merge #3159bors[bot]2020-02-259-40/+247
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3159: Server-side Semantic Tokens r=matklad a=kjeremy Takes the output of `syntax_highlighting` and converts it to the proposed semantic tokens API (so far only `textDocument/semanticTokens`. There's a lot of cool stuff we could do with this and the "Inspect Editor Tokens and Scopes" vscode command (pic below) is a cool way to see what has tokens and what doesn't. Incredibly hacky and could panic due to unwraps, `panic!` etc. To use: run with `code-insiders --enable-proposed-api matklad.rust-analyzer`. If you try to run this without `--enable-proposed-api` it will crash. ![image](https://user-images.githubusercontent.com/4325700/74595603-7c66cf00-5011-11ea-9593-312663f04fc1.png) @matklad I'm mostly looking for design feedback. Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * | | Add docsJeremy Kolb2020-02-251-0/+8
| | | |
| * | | Teach the server about Semantic Tokens proposed LSPkjeremy2020-02-259-40/+239
| | | |
* | | | Merge #3299bors[bot]2020-02-2515-198/+203
|\ \ \ \ | |/ / / |/| | | | | | | | | | | | | | | | | | | | | | | 3299: vscode: migrate to request type api r=matklad a=Veetaha More type-safety to the god of type-safety. Co-authored-by: Veetaha <[email protected]>
| * | | vscode: migrate rust-analyzer-api to import * as lc as per matklad and kjeremyVeetaha2020-02-241-23/+23
| | | |
| * | | vscode: run fmtVeetaha2020-02-241-1/+1
| | | |
| * | | vscode: migrate inlay_hints to rust-analyzer-api.tsVeetaha2020-02-242-31/+16
| | | |
| * | | vscode: migrate syntax_tree to rust-analyzer-api.tsVeetaha2020-02-241-20/+7
| | | |
| * | | vscode: migrate ssr to rust-analyzer-api.tsVeetaha2020-02-241-11/+5
| | | |
| * | | vscode: migrate runnables to rust-analyzer-api.tsVeetaha2020-02-241-22/+7
| | | |
| * | | vscode: migrate parent_module to rust-analyzer-api.tsVeetaha2020-02-241-7/+3
| | | |
| * | | vscode: migrate on_enter to rust-analyzer-api.tsVeetaha2020-02-241-14/+7
| | | |
| * | | vscode: migrate matching_brace to rust-analyzer-api.tsVeetaha2020-02-241-12/+3
| | | |
| * | | vscode: migrate join_lines to rust-analyzer-api.tsVeetaha2020-02-241-13/+4
| | | |
| * | | vscode: migrate collectGarbage to rust-analyzer-api.tsVeetaha2020-02-241-5/+4
| | | |
| * | | vscode: migrate expand_macro to rust-analyzer-api.tsVeetaha2020-02-241-13/+5
| | | |
| * | | vscode: migrate analyzer_status to rust-analyzer-api.tsVeetaha2020-02-241-4/+2
| | | |
| * | | vscode: migrate highlighting to rust-analyzer-api.tsVeetaha2020-02-241-39/+21
| | | |
| * | | vscode: migrate source_cnage.rs to rust-analyzer-api.rsVeetaha2020-02-241-7/+2
| | | |
| * | | vscode: create rust-analyzer-api.tsVeetaha2020-02-241-0/+117
| |/ /
* | | Merge #3296bors[bot]2020-02-242-4/+4
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3296: vscode: bump TypeScript version r=matklad a=Veetaha There is a new [`type-only` import and export feature](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#-type-only-imports-and-export), but let's keep our codebase as simple as it is now. Also, top-level await :tada:, though with a caveat )) ![image](https://user-images.githubusercontent.com/36276403/75185341-93629b00-574e-11ea-8d5c-4a4293f140f7.png) Co-authored-by: Veetaha <[email protected]>
| * | vscode: bump TypeScript versionVeetaha2020-02-242-4/+4
|/ /
* | Merge #3294bors[bot]2020-02-242-8/+53
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3294: When joining lines, unwrap trivial diverging blocks r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | When joining lines, unwrap trivial diverging blocksAleksey Kladov2020-02-242-8/+53
| | |
* | | Merge #3293bors[bot]2020-02-241-2/+2
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | 3293: Cleanp r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | CleanpAleksey Kladov2020-02-241-2/+2
|/ /
* | Merge #3291bors[bot]2020-02-241-6/+6
|\ \ | | | | | | | | | | | | | | | | | | | | | 3291: Update deps r=kjeremy a=kjeremy Co-authored-by: Jeremy Kolb <[email protected]>
| * | Update depsJeremy Kolb2020-02-241-6/+6
|/ /
* | Merge #3290bors[bot]2020-02-241-0/+6
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3290: Don't block onEnter if request fails r=matklad a=matklad closes #3286 bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Don't block onEnter if request failsAleksey Kladov2020-02-241-0/+6
| | | | | | | | | | | | closes #3286
* | | Merge #3288bors[bot]2020-02-241-2/+5
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3288: Quick fix circular json error when sanity-check fails r=matklad a=Veetaha Related issue: #3280 Co-authored-by: Veetaha <[email protected]>
| * | | Quick fix circular json error when sanity-check failsVeetaha2020-02-241-2/+5
| | | | | | | | | | | | Related issue: #3280
* | | | Merge #3289bors[bot]2020-02-241-0/+23
|\ \ \ \ | |/ / / |/| / / | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | 3289: Don't break onEnter if rust-analyzer fails to start r=matklad a=matklad closes #3253 bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * / Don't break onEnter if rust-analyzer fails to startAleksey Kladov2020-02-241-0/+23
|/ / | | | | | | closes #3253
* | Merge #3287bors[bot]2020-02-241-92/+125
|\ \ | |/ |/| | | | | | | | | | | | | 3287: Omit type hints for enum variant bind pats r=matklad a=SomeoneToIgnore After using new hints for a while, I've started to think that hints for enum variants are an overkill. Another user also shares the same toughts: https://github.com/rust-analyzer/rust-analyzer/issues/3273#issuecomment-590172297 Co-authored-by: Kirill Bulatov <[email protected]>
| * Omit type hints for enum variant bind patsKirill Bulatov2020-02-241-92/+125
|/
* Merge #3277bors[bot]2020-02-234-44/+60
|\ | | | | | | | | | | | | | | | | | | 3277: vscode: gracefully handle cancellation errors r=matklad a=Veetaha This PR fixes a fleet of errors that rapidly populate the Developer Tools console. ![image](https://user-images.githubusercontent.com/36276403/75097665-0c7aba80-55b6-11ea-8edd-ab5dc5f89e1e.png) Co-authored-by: Veetaha <[email protected]>
| * vscode: gracefully handle cancellation errorsVeetaha2020-02-234-44/+60
| |
* | Merge #3282bors[bot]2020-02-231-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | 3282: Add suggestion for failed path resolution r=matklad a=yoshuawuyts This adds https://github.com/rust-analyzer/rust-analyzer/issues/3245 as an inline help text for when path resolution fails. I saw this error, but also `"Failed to read Cargo metadata from Cargo.toml file"` several times while trying to debug what was failing. There's probably a more structured way of displaying help texts in VS Code popups. But this would've saved me 20 mins of debugging when installing `rust-analyzer` under WSL today. Thanks! Co-authored-by: Yoshua Wuyts <[email protected]>
| * Add suggestion for failed path resolutionYoshua Wuyts2020-02-231-1/+1
|/ | | | This adds https://github.com/rust-analyzer/rust-analyzer/issues/3245 as an inline help text for when path resolution fails.
* Merge #3279bors[bot]2020-02-232-41/+188
|\ | | | | | | | | | | | | | | 3279: Add basic parameter name hints heuristics r=matklad a=SomeoneToIgnore Co-authored-by: Kirill Bulatov <[email protected]>
| * Style fixesKirill Bulatov2020-02-231-3/+4
| |
| * Add basic parameter name hints heuristicsKirill Bulatov2020-02-232-41/+187
| |
* | Merge #3261bors[bot]2020-02-2310-21/+51
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3261: Extract client-side logging r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * | Extract client-side loggingAleksey Kladov2020-02-2210-21/+51
| | |
* | | Merge #3275bors[bot]2020-02-231-0/+15
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | 3275: Add Structural Search and Replace doc r=matklad a=adamrk Addresses the first point of https://github.com/rust-analyzer/rust-analyzer/issues/3186. Co-authored-by: adamrk <[email protected]> Co-authored-by: Adam Bratschi-Kaye <[email protected]>
| * | rewording and typo fixAdam Bratschi-Kaye2020-02-221-1/+1
| | | | | | | | | Co-Authored-By: Laurențiu Nicola <[email protected]>
| * | add ssr docadamrk2020-02-221-0/+15
| |/
* | Merge #3278bors[bot]2020-02-231-135/+174
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3278: Show more inlay hints r=matklad a=SomeoneToIgnore Closes https://github.com/rust-analyzer/rust-analyzer/issues/3273 As suggested in https://github.com/rust-analyzer/rust-analyzer/pull/1606#discussion_r308146363 , there is a simpler way to handle inlay hints after https://github.com/rust-analyzer/rust-analyzer/issues/1618 is closed. This PR uses the approach suggested (which results in more type hints for various bindings) and also adds more name hints for function parameters. Examples can be found in the issue: * https://github.com/rust-analyzer/rust-analyzer/issues/3273#issuecomment-589998051 * https://github.com/rust-analyzer/rust-analyzer/issues/3273#issuecomment-590002839 Co-authored-by: Kirill Bulatov <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-24 21:44:13 +0000