aboutsummaryrefslogtreecommitdiff
path: root/crates
Commit message (Collapse)AuthorAgeFilesLines
* Merge #143bors[bot]2018-10-208-5/+164
|\ | | | | | | | | | | | | | | | | | | 143: Implement Find All References and Rename for local variables r=matklad a=kjeremy Expose `find_all_refs` in `Analysis`. This currently only works for local variables. Use this in the LSP to implement find all references and rename. Co-authored-by: Jeremy A. Kolb <[email protected]>
| * LSP: Add support for prepareRenameJeremy A. Kolb2018-10-192-1/+24
| |
| * Handle renaming of local variablesJeremy A. Kolb2018-10-183-2/+45
| |
| * Implement Find All References for local variablesJeremy A. Kolb2018-10-188-3/+96
| |
* | Update rowanAleksey Kladov2018-10-177-42/+19
|/
* rename gen-kinds to gen-syntaxAleksey Kladov2018-10-167-8/+8
|
* fix testsAleksey Kladov2018-10-163-46/+23
|
* Switch to published teraronAleksey Kladov2018-10-163-123/+1
|
* extract teraronAleksey Kladov2018-10-165-72/+149
|
* Cargo FormatJeremy A. Kolb2018-10-1676-1524/+1930
| | | | Run `cargo fmt` and ignore generated files
* Merge #128bors[bot]2018-10-163-66/+93
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 128: Add a test to verify if the generated codes are up-to-date. r=matklad a=mominul This test checks if the generated codes are up-to-date every time during `cargo test`. I have confirmed that the test works by manually editing the `grammar.ron` file. Closes #126 Thanks! Co-authored-by: Muhammad Mominul Huque <[email protected]>
| * take `&Path` instead of `PathBuf`Muhammad Mominul Huque2018-10-163-5/+5
| |
| * Refactor the constantsMuhammad Mominul Huque2018-10-153-20/+19
| |
| * Use CARGO_MANIFEST_DIR for locating the grammar.ron fileMuhammad Mominul Huque2018-10-153-8/+7
| |
| * Show how to generate code with error messageMuhammad Mominul Huque2018-10-143-6/+8
| |
| * create cli.rs and make the tests passingMuhammad Mominul Huque2018-10-143-59/+86
| |
* | switch to salsa releaseAleksey Kladov2018-10-151-1/+1
| |
* | 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-153-7/+8
| |
* | migrate modue map to salsaAleksey Kladov2018-10-155-165/+172
| |
* | start salsa migrationAleksey Kladov2018-10-157-92/+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-151-2/+1
| |
* | 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
| |
* | Run cargo fixAleksey Kladov2018-10-1524-44/+44
| |
* | Merge #127bors[bot]2018-10-155-77/+185
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-121-19/+19
| |/
* | 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 #122bors[bot]2018-10-1119-49/+56
|\ | | | | | | | | | | | | | | | | | | | | | | 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-1119-49/+56
| |
* | 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
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 15:53:53 +0000