aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * Check installed extensionCaio2019-03-052-12/+45
| |
* | Merge #941bors[bot]2019-03-061-10/+10
|\ \ | | | | | | | | | | | | | | | | | | | | | 941: :arrow_up: vfs r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | :arrow_up: vfsAleksey Kladov2019-03-061-108/+108
| | |
* | | Merge #940bors[bot]2019-03-0610-54/+110
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 940: Show workspace loaded notification r=matklad a=vipentti This fixes #935 This adds support for more `InitializationOptions` which are provided by the client. Co-authored-by: Ville Penttinen <[email protected]>
| * | | Add showWorkspaceLoadedNotification to vscode clientVille Penttinen2019-03-068-22/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows users to control whether or not they want to see the "workspace loaded" notification. This is done on the server side using InitializationOptions which are provided by the client. By default show_workspace_loaded is true, meaning the notification is sent.
| * | | Rename feedback to show_messageVille Penttinen2019-03-053-13/+13
| | | |
| * | | Remove InternalFeedbackVille Penttinen2019-03-051-7/+0
| | | |
| * | | Send an actual ShowMessage instead of InternalFeedback in feedback()Ville Penttinen2019-03-053-20/+27
|/ / / | | | | | | | | | | | | | | | | | | This now allows us to send a notification that can be shown in the UI when the workspace has been loaded. Additionally this removes the need for internal_mode flag.
* | | Merge #938bors[bot]2019-03-056-114/+114
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 938: Updates r=matklad a=kjeremy Co-authored-by: kjeremy <[email protected]>
| * | Updateskjeremy2019-03-056-114/+114
|/ /
* | Merge #936bors[bot]2019-03-051-1/+8
|\ \ | | | | | | | | | | | | | | | | | | | | | 936: dont produce giant debug dumps r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | dont produce giant debug dumpsAleksey Kladov2019-03-051-1/+8
|/ /
* | Merge #934bors[bot]2019-03-053-8/+32
|\ \ | | | | | | | | | | | | | | | | | | | | | 934: show message in client's UI if workspace fails to load r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | show message in client's UI if workspace fails to loadAleksey Kladov2019-03-053-8/+32
|/ /
* | Merge #930bors[bot]2019-03-054-7/+188
|\ \ | | | | | | | | | | | | | | | | | | | | | 930: Add support for parsing multiple if and while-let patterns r=matklad a=vipentti Co-authored-by: Ville Penttinen <[email protected]>
| * | Introduce pattern_list to parse pipe separated patternsVille Penttinen2019-03-052-10/+18
| | | | | | | | | | | | | | | pattern_list comes in two variants, one uses the default PAT_RECOVERY_SET as the recovery set, while other allows the user to provide a recovery set.
| * | Add support for parsing multiple if and while-let patternsVille Penttinen2019-03-043-1/+174
| |/
* | Merge #912bors[bot]2019-03-054-24/+116
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 912: Make goto definition/hover work for associated items r=matklad a=kjeremy Just functions so far. Looking for comments. Fixes #911 Towards #832 Co-authored-by: kjeremy <[email protected]> Co-authored-by: Jeremy Kolb <[email protected]>
| * Use impl_froms!kjeremy2019-03-041-13/+3
| |
| * Make ExpOrPatId privatekjeremy2019-03-042-4/+7
| |
| * FormatJeremy Kolb2019-03-041-7/+2
| |
| * Add NavigationTarget::from_impl_itemJeremy Kolb2019-03-042-14/+22
| |
| * Remove commented out codeJeremy Kolb2019-03-041-9/+0
| |
| * Use ImplItems instead of just FunctionJeremy Kolb2019-03-043-40/+65
| |
| * Make goto definition/hover resolve constructorskjeremy2019-03-043-7/+87
| |
* | Merge #929bors[bot]2019-03-043-12/+28
|\ \ | | | | | | | | | | | | | | | | | | | | | 929: allow `mut ident` patterns in trait methods r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | allow `mut ident` patterns in trait methodsAleksey Kladov2019-03-043-12/+28
|/ / | | | | | | closes #928
* | Merge #927bors[bot]2019-03-044-2/+21
|\ \ | |/ |/| | | | | | | | | | | 927: allow aliases in underscores r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * allow aliases in underscoresAleksey Kladov2019-03-044-2/+21
|/ | | | | | | | this helps with use foo::Trait as _; syntax
* Merge #926bors[bot]2019-03-043-1/+56
|\ | | | | | | | | | | | | | | 926: allow vararg functions r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * allow vararg functionsAleksey Kladov2019-03-043-1/+56
| |
* | Merge #925bors[bot]2019-03-045-61/+83
|\ \ | |/ |/| | | | | | | | | | | 925: improve error recovery r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * improve error recoveryAleksey Kladov2019-03-044-59/+77
| | | | | | | | parse the contents of error block as an expression
| * extract block contents into a functionAleksey Kladov2019-03-041-2/+6
|/
* Merge #916bors[bot]2019-03-044-72/+220
|\ | | | | | | | | | | | | | | 916: Error handling for macros r=matklad a=detrumi Part of #720 Co-authored-by: Wilco Kusee <[email protected]>
| * Add expander unit testsWilco Kusee2019-03-031-4/+69
| |
| * Add parser unit testsWilco Kusee2019-03-033-6/+58
| |
| * Split parse and expand errorsWilco Kusee2019-03-034-72/+74
| |
| * FormattingWilco Kusee2019-03-021-10/+20
| |
| * Replace option with result in mbeWilco Kusee2019-03-024-74/+93
| |
* | Merge #924bors[bot]2019-03-0410-43/+423
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 924: Improve show syntax tree r=matklad a=vipentti This implements some of the features discussed in #820. You can now select a range of syntax in a file and then use "Show Syntax Tree" to show its syntax. In addition you can select a range of syntax that is inside a string (typically test cases) and show its syntax as well. Previous behavior is still available, simply use "Show Syntax Tree" without a selection, and you get the live updating syntax tree. Additionally now the live updating tree will update when the active file is changed. Previously you had to type something in the new file to get the syntax tree to update. Co-authored-by: Ville Penttinen <[email protected]>
| * | Allow syntax strings to contain test markersVille Penttinen2019-03-041-1/+3
| | | | | | | | | | | | | | | We simply remove all the CUSTOM_MARKERS before attempting to parse the file. This allows for the syntax selection to work with most of the test strings.
| * | Implement syntax tree support for syntax inside stringVille Penttinen2019-03-043-8/+206
| | | | | | | | | | | | | | | | | | This allows us to select a string or portions of it and try parsing it as rust syntax. This is mostly helpful when developing tests where the test itself contains some rust syntax as a string.
| * | Allow syntax tree to update when changing filesVille Penttinen2019-03-032-17/+26
| | | | | | | | | | | | | | | | | | Previously when using the file based syntax tree, it would not update until a change had been made in the new file. Now we automatically update the syntax tree to match the current file.
| * | Rename syntaxtree text provider to SyntaxTreeContentProviderVille Penttinen2019-03-033-13/+11
| | |
| * | Add vscode support for range in SyntaxTreeParamsVille Penttinen2019-03-033-11/+41
| | | | | | | | | | | | | | | | | | This enables the client to use a command to either show the live-updating version of the syntax tree for the current file. Or optionally when a selected range is provided, we then provide a snapshot of the syntax tree for the range.
| * | Add optional range parameter to SyntaxTreeParamsVille Penttinen2019-03-034-5/+148
|/ / | | | | | | | | When range is provided, instead of showing the syntax for the whole file, we'll show the syntax tree for the given range.
* | Merge #917bors[bot]2019-03-0350-1291/+1286
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 917: Trait tests r=flodiebold a=flodiebold This adds a bunch of basic tests for trait functionality, just to outline what seems like the first goals for that ;) It also changes the display of `Ty::Unknown` to `{unknown}`, since `[unknown]` could be confused with a slice, and fixes an error in the emacs runnables code. Co-authored-by: Florian Diebold <[email protected]>
| * | Inline type inference test snapshotsFlorian Diebold2019-03-0359-1504/+1096
| | |
| * | emacs: Fix (void-variable rust-analyzer--last-runnable)Florian Diebold2019-03-031-1/+1
| | |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 02:50:08 +0000