aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/grammar.ron
Commit message (Collapse)AuthorAgeFilesLines
...
* Make let statements kind of workFlorian Diebold2018-12-231-0/+1
|
* Parse integer / float typesFlorian Diebold2018-12-231-1/+1
|
* Add beginnings of type infrastructureFlorian Diebold2018-12-231-7/+7
|
* Clarify and correct comment about multi_byte_tokensDJMcNab2018-12-081-2/+2
|
* Validate byte string literalsAdolfo Ochagavía2018-11-111-0/+1
|
* Add validator for byteAdolfo Ochagavía2018-11-111-0/+1
|
* Validate string literalsAdolfo Ochagavía2018-11-091-0/+1
|
* rename ROOT -> SOURCE_FILEAleksey Kladov2018-11-071-2/+2
|
* Add some more DocCommentsOwnerJeremy A. Kolb2018-11-071-2/+7
|
* Add character literal parsing and validationAdolfo Ochagavía2018-11-041-0/+1
|
* Remove DOC_COMMENTJeremy A. Kolb2018-10-311-1/+0
| | | | Closes #166
* `ast::DocCommentsOwner` which represents a documentation comment ownerJeremy A. Kolb2018-10-311-0/+1
|
* Complete crate:: pathsAleksey Kladov2018-10-241-1/+2
|
* rename gen-kinds to gen-syntaxAleksey Kladov2018-10-161-1/+1
|
* Merge #127bors[bot]2018-10-151-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 elementsAdolfo Ochagavía2018-10-121-0/+1
| |
* | Language Server: textDocument/signatureHelpJeremy A. Kolb2018-10-111-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 wrapperAdolfo Ochagavía2018-10-111-0/+1
|
* Add `cargo gen-kinds` documentationDaniel McNab2018-10-041-1/+4
|
* rename all thingsAleksey Kladov2018-09-161-0/+538