Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | :arrow_up: vfs | Aleksey Kladov | 2019-08-25 | 3 | -5/+9 |
| | |||||
* | rename struct -> record, pos -> tuple | Aleksey Kladov | 2019-08-23 | 1 | -1/+1 |
| | |||||
* | implement feature flags | Aleksey Kladov | 2019-08-22 | 3 | -22/+48 |
| | |||||
* | show error to the user when deserializing config | Aleksey Kladov | 2019-08-22 | 3 | -8/+22 |
| | |||||
* | fix default for the exlude key | Aleksey Kladov | 2019-08-21 | 2 | -2/+6 |
| | |||||
* | remove debug-print | Aleksey Kladov | 2019-08-20 | 1 | -1/+0 |
| | |||||
* | switch to upstream ra_vfs | Aleksey Kladov | 2019-08-20 | 1 | -1/+1 |
| | |||||
* | Drop unnecessary `&'_` from impls | Aleksey Kladov | 2019-08-20 | 1 | -20/+20 |
| | |||||
* | refactor TryConvWith similar to ConvWith | Aleksey Kladov | 2019-08-20 | 1 | -42/+26 |
| | |||||
* | translate \n -> \r\n on the way out | Aleksey Kladov | 2019-08-20 | 4 | -19/+33 |
| | |||||
* | make CTX type param instead of assoc type | Aleksey Kladov | 2019-08-20 | 1 | -34/+25 |
| | | | | that way, we can implement ConvWith<&'_ CTX> for different lifetimes | ||||
* | add tests for crlf | Aleksey Kladov | 2019-08-20 | 1 | -0/+46 |
| | |||||
* | minor | Aleksey Kladov | 2019-08-20 | 1 | -1/+1 |
| | |||||
* | don't load sysroot in most heavy tests | Aleksey Kladov | 2019-08-19 | 5 | -12/+33 |
| | |||||
* | update lsp | Aleksey Kladov | 2019-08-17 | 3 | -6/+2 |
| | |||||
* | implement durability | Aleksey Kladov | 2019-08-15 | 1 | -0/+1 |
| | |||||
* | Drop support for old extendSelection API | Aleksey Kladov | 2019-08-12 | 3 | -44/+1 |
| | | | | | | Emacs now handles this via native LSP request https://github.com/emacs-lsp/lsp-mode/commit/dc86bbb227147aa8141e690ad5648fdbd2ebdb9f | ||||
* | Always set the runnable name | Kirill Bulatov | 2019-08-09 | 1 | -11/+11 |
| | |||||
* | Extract common logic | Kirill Bulatov | 2019-08-09 | 1 | -55/+42 |
| | |||||
* | Show backtraces in lens runnables | Kirill Bulatov | 2019-08-09 | 1 | -1/+5 |
| | |||||
* | Merge #1652 | bors[bot] | 2019-08-06 | 2 | -14/+2 |
|\ | | | | | | | | | | | | | | | | | | | | | | | 1652: Improve type hints behavior r=matklad a=SomeoneToIgnore This PR fixed the following type hints issues: * Restructures the `InlayKind` enum contents based on the discussion here: https://github.com/rust-analyzer/rust-analyzer/pull/1606#issuecomment-515968055 * Races described in #1639 * Caches the latest decorations received for each file to show them the next time the file is opened (instead of a new server request) Co-authored-by: Kirill Bulatov <[email protected]> | ||||
| * | Use proper inlay kinds | Kirill Bulatov | 2019-08-04 | 2 | -14/+2 |
| | | |||||
* | | fix tests | Aleksey Kladov | 2019-08-06 | 1 | -2/+2 |
| | | |||||
* | | allow to exclude certain files and directories | Aleksey Kladov | 2019-08-06 | 3 | -14/+29 |
| | | |||||
* | | rename config | Aleksey Kladov | 2019-08-06 | 4 | -19/+14 |
| | | |||||
* | | introduce ra_vfs_glob crate | Aleksey Kladov | 2019-08-06 | 4 | -59/+17 |
| | | | | | | | | It manages exclusion rules for the vfs crate | ||||
* | | cleanup | Aleksey Kladov | 2019-08-06 | 2 | -2/+2 |
| | | |||||
* | | rename | Aleksey Kladov | 2019-08-06 | 1 | -9/+9 |
| | | |||||
* | | use Conv for severity | Aleksey Kladov | 2019-08-06 | 2 | -20/+21 |
| | | |||||
* | | Add test for #1540 | Jeremy Kolb | 2019-08-03 | 1 | -0/+17 |
|/ | |||||
* | remove-comment | kjeremy | 2019-07-31 | 1 | -1/+0 |
| | |||||
* | Add explicit newline preserving tests | kjeremy | 2019-07-31 | 1 | -0/+6 |
| | |||||
* | Fixed review comments | Roman Stoliar | 2019-07-30 | 1 | -3/+9 |
| | |||||
* | Hide comments in rust section of doc comments | Roman Stoliar | 2019-07-30 | 3 | -5/+21 |
| | |||||
* | Support destructuring patterns | Kirill Bulatov | 2019-07-28 | 2 | -0/+6 |
| | |||||
* | Improve inlay hinting for types | Kirill Bulatov | 2019-07-26 | 2 | -0/+4 |
| | | | | | | Add hints for types in for loop expressions. Resolve types for every tuple parameter. Refactor the code. | ||||
* | Make Analysis api cancellable | Kirill Bulatov | 2019-07-25 | 3 | -37/+48 |
| | |||||
* | Merge #1549 | bors[bot] | 2019-07-23 | 3 | -1/+50 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1549: Show type lenses for the resolved let bindings r=matklad a=SomeoneToIgnore Types that are fully unresolved are not displayed: <img width="279" alt="image" src="https://user-images.githubusercontent.com/2690773/61518122-8e4ba980-aa11-11e9-9249-6d9f9b202e6a.png"> A few concerns that I have about the current implementation: * I've adjusted the `file_structure` API method to return the information about the `let` bindings. Although it works fine, I have a feeling that adding a new API method would be the better way. But this requires some prior discussion, so I've decided to go for an easy way with an MVP. Would be nice to hear your suggestions. * There's a hardcoded `{undersolved}` check that I was forced to use, since the method that resolves types returns a `String`. Is there a better typed API I can use? This will help, for instance, to add an action to the type lenses that will allow us to navigate to the type. Co-authored-by: Kirill Bulatov <[email protected]> | ||||
| * | Code review fixes | Kirill Bulatov | 2019-07-22 | 3 | -1/+50 |
| | | |||||
| * | Do not show the lens with type hints | Kirill Bulatov | 2019-07-21 | 1 | -13/+4 |
| | | |||||
| * | Resolve types on the server | Kirill Bulatov | 2019-07-21 | 1 | -25/+10 |
| | | |||||
| * | Refactor server api | Kirill Bulatov | 2019-07-20 | 1 | -28/+42 |
| | | |||||
| * | If possible, show type lenses for the let bindings | Kirill Bulatov | 2019-07-20 | 1 | -16/+26 |
| | | |||||
* | | flexi_logger 0.14 | kjeremy | 2019-07-22 | 1 | -1/+1 |
|/ | |||||
* | Add "Run" lens for binary runnables | Kirill Bulatov | 2019-07-16 | 1 | -1/+1 |
| | |||||
* | cargo update | kjeremy | 2019-07-15 | 1 | -1/+1 |
| | |||||
* | Remove executeCommandProvider: apply_code_action. | Michael Bolin | 2019-07-11 | 2 | -10/+8 |
| | | | | | | | | | | | | | | | | | | | This appears to have been introduced ages ago in https://github.com/rust-analyzer/rust-analyzer/commit/be742a587704f27f4e503c50f549aa9ec1527fcc but has since been removed. As it stands, it is problematic if multiple instances of the rust-analyzer LSP are launched during the same VS Code session because VS Code complains about multiple LSP servers trying to register the same command. Most LSP servers workaround this by parameterizing the command by the process id. For example, this is where `rls` does this: https://github.com/rust-lang/rls/blob/ff0b9057c8f62bc4f8113d741e96c9587ef1a817/rls/src/server/mod.rs#L413-L421 Though `apply_code_action` does not seems to be used, so it seems better to delete it than to parameterize it. | ||||
* | Ignore workspace/didChangeConfiguration notifications. | Michael Bolin | 2019-07-11 | 2 | -4/+11 |
| | |||||
* | Remove unused dependencies | Shotaro Yamada | 2019-07-08 | 1 | -1/+0 |
| | |||||
* | don't send LocationLink unless the client opts-in | Aleksey Kladov | 2019-07-08 | 5 | -12/+62 |
| | | | | closes #1474 |