aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/ast
Commit message (Collapse)AuthorAgeFilesLines
...
* Add AST definitions for struct/variant fields etc.Florian Diebold2018-12-251-7/+218
| | | | Fixes #117
* Infer result of struct literals, and recurse into their child expressionsFlorian Diebold2018-12-251-3/+23
|
* Resolve paths to defs (functions currently) during type inferenceFlorian Diebold2018-12-231-1/+5
|
* Make let statements kind of workFlorian Diebold2018-12-231-0/+4
|
* Parse integer / float typesFlorian Diebold2018-12-231-1/+5
|
* Add beginnings of type infrastructureFlorian Diebold2018-12-231-6/+38
|
* grand module renameAleksey Kladov2018-12-081-365/+0
|
* Some import resolution boilerplateAleksey Kladov2018-11-201-0/+6
|
* Validate byte string literalsAdolfo Ochagavía2018-11-112-0/+43
|
* Add validator for byteAdolfo Ochagavía2018-11-112-0/+43
|
* Validate string literalsAdolfo Ochagavía2018-11-092-1/+45
|
* Complete paths in use treesAleksey Kladov2018-11-071-0/+9
|
* rename ROOT -> SOURCE_FILEAleksey Kladov2018-11-071-43/+43
|
* Add some more DocCommentsOwnerJeremy A. Kolb2018-11-071-0/+7
|
* ra_syntax::File is just RootNodeAleksey Kladov2018-11-062-197/+961
|
* Add a pinch of commentsAleksey Kladov2018-11-063-0/+16
|
* Generalize Owned nodesAleksey Kladov2018-11-062-1806/+1237
|
* Add character literal parsing and validationAdolfo Ochagavía2018-11-042-0/+40
|
* Use From to get an owned ASTAleksey Kladov2018-11-012-400/+700
|
* Reformat allAleksey Kladov2018-10-311-5/+11
|
* `ast::DocCommentsOwner` which represents a documentation comment ownerJeremy A. Kolb2018-10-312-0/+19
|
* Move FnDescriptors to analyzerAleksey Kladov2018-10-312-100/+100
|
* Introduce owned ast nodesAleksey Kladov2018-10-312-2/+1303
| | | | ast::FooNode is an owned 'static counterpart to ast::Foo<'a>
* Complete crate:: pathsAleksey Kladov2018-10-242-0/+34
|
* clippy: Use if lets and remove redundant returnsAlan Du2018-10-181-3/+2
|
* rename gen-kinds to gen-syntaxAleksey Kladov2018-10-162-2/+2
|
* Cargo FormatJeremy A. Kolb2018-10-163-13/+15
| | | | Run `cargo fmt` and ignore generated files
* regenerateAleksey Kladov2018-10-151-1/+1
|
* Run cargo fixAleksey Kladov2018-10-152-2/+2
|
* Merge #127bors[bot]2018-10-152-3/+43
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]>
| * Only fold groups of similar commentsAdolfo Ochagavía2018-10-131-1/+1
| |
| * Cleanup fold code and split logic to fold single elementsAdolfo Ochagavía2018-10-122-2/+42
| |
* | RegenerateJeremy A. Kolb2018-10-121-1/+2
| |
* | Language Server: textDocument/signatureHelpJeremy A. Kolb2018-10-111-1/+4
|/ | | | | | | | | | 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 #116bors[bot]2018-10-112-0/+61
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]>
| * Use Comment wrapperAdolfo Ochagavía2018-10-112-0/+61
| |
* | Update crates/ra_syntax/src/ast/generated.rsReinier Maas2018-10-101-32/+64
| | | | | | | | effect of running cargo gen-kinds
* | Update generated.rs.teraReinier Maas2018-10-101-2/+1
|/ | | Removing `-` for #114
* Add `cargo gen-kinds` documentationDaniel McNab2018-10-042-0/+8
|
* Move to rowan for syntax tree implAleksey Kladov2018-10-021-7/+6
|
* rename all thingsAleksey Kladov2018-09-163-0/+2431
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-12 05:02:07 +0000