| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Clarify and correct comment about multi_byte_tokens | DJMcNab | 2018-12-08 | 1 | -2/+2 | |
| | | ||||||
| * | Validate byte string literals | Adolfo Ochagavía | 2018-11-11 | 1 | -0/+1 | |
| | | ||||||
| * | Add validator for byte | Adolfo Ochagavía | 2018-11-11 | 1 | -0/+1 | |
| | | ||||||
| * | Validate string literals | Adolfo Ochagavía | 2018-11-09 | 1 | -0/+1 | |
| | | ||||||
| * | rename ROOT -> SOURCE_FILE | Aleksey Kladov | 2018-11-07 | 1 | -2/+2 | |
| | | ||||||
| * | Add some more DocCommentsOwner | Jeremy A. Kolb | 2018-11-07 | 1 | -2/+7 | |
| | | ||||||
| * | Add character literal parsing and validation | Adolfo Ochagavía | 2018-11-04 | 1 | -0/+1 | |
| | | ||||||
| * | Remove DOC_COMMENT | Jeremy A. Kolb | 2018-10-31 | 1 | -1/+0 | |
| | | | | | Closes #166 | |||||
| * | `ast::DocCommentsOwner` which represents a documentation comment owner | Jeremy A. Kolb | 2018-10-31 | 1 | -0/+1 | |
| | | ||||||
| * | Complete crate:: paths | Aleksey Kladov | 2018-10-24 | 1 | -1/+2 | |
| | | ||||||
| * | rename gen-kinds to gen-syntax | Aleksey Kladov | 2018-10-16 | 1 | -1/+1 | |
| | | ||||||
| * | Merge #127 | bors[bot] | 2018-10-15 | 1 | -0/+1 | |
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]> | |||||
| | * | Cleanup fold code and split logic to fold single elements | Adolfo Ochagavía | 2018-10-12 | 1 | -0/+1 | |
| | | | ||||||
| * | | Language Server: textDocument/signatureHelp | Jeremy A. Kolb | 2018-10-11 | 1 | -1/+1 | |
| |/ | | | | | | | | | | 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 | |||||
| * | Use Comment wrapper | Adolfo Ochagavía | 2018-10-11 | 1 | -0/+1 | |
| | | ||||||
| * | Add `cargo gen-kinds` documentation | Daniel McNab | 2018-10-04 | 1 | -1/+4 | |
| | | ||||||
| * | rename all things | Aleksey Kladov | 2018-09-16 | 1 | -0/+538 | |
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |