aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * create cli.rs and make the tests passingMuhammad Mominul Huque2018-10-143-59/+86
| |
* | Merge #101bors[bot]2018-10-1522-1064/+432
|\ \ | | | | | | | | | | | | | | | | | | | | | 101: migrate to salsa-rs/salsa r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | switch to salsa releaseAleksey Kladov2018-10-152-5/+5
| | |
| * | SimplifyAleksey Kladov2018-10-152-13/+0
| | |
| * | remove clonesAleksey Kladov2018-10-154-6/+5
| | |
| * | make analysis syncAleksey Kladov2018-10-154-19/+37
| | |
| * | Tweak writable root APIAleksey Kladov2018-10-152-11/+8
| | |
| * | remove resolver from worldAleksey Kladov2018-10-151-2/+0
| | |
| * | Drop dead codeAleksey Kladov2018-10-154-401/+0
| | |
| * | fix testsAleksey Kladov2018-10-154-12/+21
| | |
| * | Switch to the master of salsaAleksey Kladov2018-10-154-10/+13
| | |
| * | migrate modue map to salsaAleksey Kladov2018-10-155-165/+172
| | |
| * | start salsa migrationAleksey Kladov2018-10-158-100/+221
| | |
| * | remove our own copy of salsaAleksey Kladov2018-10-153-471/+0
| | | | | | | | | | | | salsa-rs/salsa is faster and more type safe
| * | add salsa dep, break the worldAleksey Kladov2018-10-152-102/+203
|/ /
* | Merge #132bors[bot]2018-10-151-0/+2
|\ \ | | | | | | | | | | | | | | | | | | | | | 132: Cache caro on Travis r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | Cache caro on TravisAleksey Kladov2018-10-151-0/+2
| | |
* | | Merge #129bors[bot]2018-10-1566-98/+154
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | 129: 2018 r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | regenerateAleksey Kladov2018-10-151-1/+1
| | |
| * | Parse crate paths in expressionsAleksey Kladov2018-10-153-1/+45
| | |
| * | migrate analysis and server to 2018Aleksey Kladov2018-10-1521-36/+42
| | |
| * | switch ra_cli to 2018Aleksey Kladov2018-10-151-0/+1
| | |
| * | switch editor to 2018Aleksey Kladov2018-10-1510-13/+14
| | |
| * | switch base crates to 2018Aleksey Kladov2018-10-153-0/+3
| | |
| * | Mention 2018 in the readmeAleksey Kladov2018-10-151-1/+2
| | |
| * | Run cargo fixAleksey Kladov2018-10-1524-44/+44
| | |
| * | Switch to betaAleksey Kladov2018-10-152-2/+2
|/ /
* | Merge #127bors[bot]2018-10-156-79/+187
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 127: Improve folding r=matklad a=aochagavia I was messing around with adding support for multiline comments in folding and ended up changing a bunch of other things. First of all, I am not convinced of folding groups of successive items. For instance, I don't see why it is worthwhile to be able to fold something like the following: ```rust use foo; use bar; ``` Furthermore, this causes problems if you want to fold a multiline import: ```rust use foo::{ quux }; use bar; ``` The problem is that now there are two possible folds at the same position: we could fold the first use or we could fold the import group. IMO, the only place where folding groups makes sense is when folding comments. Therefore I have **removed folding import groups in favor of folding multiline imports**. Regarding folding comments, I made it a bit more robust by requiring that comments can only be folded if they have the same flavor. So if you have a bunch of `//` comments followed by `//!` comments, you will get two separate fold groups instead of a single one. Finally, I rewrote the API in such a way that it should be trivial to add new folds. You only need to: * Create a new FoldKind * Add it to the `fold_kind` function that converts from `SyntaxKind` to `FoldKind` Fixes #113 Co-authored-by: Adolfo Ochagavía <[email protected]>
| * | Improve testsAdolfo Ochagavía2018-10-132-30/+63
| | |
| * | Only fold groups of similar commentsAdolfo Ochagavía2018-10-132-28/+31
| | |
| * | Cleanup fold code and split logic to fold single elementsAdolfo Ochagavía2018-10-124-40/+112
| | |
| * | Fold multiline commentsAdolfo Ochagavía2018-10-122-21/+21
| |/
* | Merge #110bors[bot]2018-10-1510-12/+315
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | 110: Signature help r=matklad a=kjeremy @matklad Once this is in shape I would like to add tests. I think a separate PR should be done for returning documentation information and markdown. Fixes #102 Co-authored-by: Jeremy A. Kolb <[email protected]>
| * | A FnDescriptor shouldn't exist without a nameJeremy A. Kolb2018-10-123-49/+47
| | |
| * | RegenerateJeremy A. Kolb2018-10-121-1/+2
| | |
| * | Language Server: textDocument/signatureHelpJeremy A. Kolb2018-10-1110-12/+316
| |/ | | | | | | | | | | | | | | | | | | Implements a pretty barebones function signature help mechanism in the language server. Users can use `Analysis::resolve_callback()` to get basic information about a call site. Fixes #102
* | Merge #112bors[bot]2018-10-143-133/+152
|\ \ | |/ |/| | | | | | | | | | | 112: brush up docs r=matklad a=matklad @kjeremy @aochagavia @DJMcNab anything else significant to add here? Co-authored-by: Aleksey Kladov <[email protected]>
| * Apply review suggestionsAleksey Kladov2018-10-141-10/+16
| |
| * brush up docsAleksey Kladov2018-10-143-133/+146
| |
* | Merge #122bors[bot]2018-10-1120-49/+68
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 122: Use rustc-hash crate r=matklad a=mominul Replace std's HashMap, HashSet with FxHashMap and FxHashSet. Closes #121 Thanks! Co-authored-by: Muhammad Mominul Huque <[email protected]>
| * | Replace HashMap, HashSet with FxHashMap and FxHashSetMuhammad Mominul Huque2018-10-1120-49/+68
| | |
* | | Merge #116bors[bot]2018-10-114-58/+199
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 116: Collapse comments upon join r=matklad a=aochagavia Todo: - [x] Write tests - [x] Resolve fixmes - [x] Implement `comment_start_length` using the parser I left a bunch of questions as fixmes. Can someone take a look at them? Also, I would love to use the parser to calculate the length of the leading characters in a comment (`//`, `///`, `//!`, `/*`), so any hints are greatly appreciated. Co-authored-by: Adolfo Ochagavía <[email protected]> Co-authored-by: Adolfo Ochagavía <[email protected]>
| * | Remove smart multiline comment joinAdolfo Ochagavía2018-10-111-22/+23
| | |
| * | Add testsAdolfo Ochagavía2018-10-111-0/+56
| | |
| * | Remove nestingAdolfo Ochagavía2018-10-111-75/+68
| | |
| * | Use Comment wrapperAdolfo Ochagavía2018-10-114-36/+78
| | |
| * | Collapse comments upon joinAdolfo Ochagavía2018-10-101-15/+64
| | |
* | | Merge #118bors[bot]2018-10-112-22/+3
|\ \ \ | |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | 118: Remove error publishing through publishDecorations r=matklad a=aochagavia The errors are already reported by `publishDiagnostics` Closes #109 Co-authored-by: Adolfo Ochagavía <[email protected]>
| * | Report errors only onceAdolfo Ochagavía2018-10-101-14/+3
| | |
| * | Remove error publishing through publishDecorationsAdolfo Ochagavía2018-10-102-8/+0
| |/
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 13:40:19 +0000