aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/ast/generated.rs
Commit message (Collapse)AuthorAgeFilesLines
* Type the self parameterFlorian Diebold2019-01-041-1/+46
|
* Add HIR for impl blocksFlorian Diebold2019-01-041-2/+38
| | | | | | | | | Since we need to be able to go from def to containing impl block, as well as the other direction, and to find all impls for a certain type, a design similar to the one for modules, where we collect all impls for the whole crate and keep them in an arena, seemed fitting. The ImplBlock type, which provides the public interface, then consists only of an Arc to the arena containing all impls, and the index into it.
* Rename ImplItem to ImplBlockFlorian Diebold2019-01-041-18/+18
| | | | | rustc uses the name ImplItem for items in impls, not the impl {} block itself, which could lead to confusion.
* visibility ownerAleksey Kladov2019-01-031-0/+47
|
* super simplistic macro expansionAleksey Kladov2018-12-281-0/+4
|
* add macro-call nodeAleksey Kladov2018-12-281-0/+41
|
* Add a hir::TypeRef as an intermediate between ast::TypeRef and ty::TyFlorian Diebold2018-12-251-5/+33
|
* Implement reference / pointer typesFlorian Diebold2018-12-251-3/+15
| | | | | - parse them - infer types of & and * expressions
* Implement basic completion for fieldsFlorian Diebold2018-12-251-0/+4
|
* Type field accessesFlorian Diebold2018-12-251-1/+9
|
* 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
|
* Validate byte string literalsAdolfo Ochagavía2018-11-111-0/+37
|
* Add validator for byteAdolfo Ochagavía2018-11-111-0/+37
|
* Validate string literalsAdolfo Ochagavía2018-11-091-0/+37
|
* 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-061-194/+948
|
* Add a pinch of commentsAleksey Kladov2018-11-061-0/+6
|
* Generalize Owned nodesAleksey Kladov2018-11-061-1788/+1223
|
* Add character literal parsing and validationAdolfo Ochagavía2018-11-041-0/+34
|
* Use From to get an owned ASTAleksey Kladov2018-11-011-396/+693
|
* `ast::DocCommentsOwner` which represents a documentation comment ownerJeremy A. Kolb2018-10-311-0/+1
|
* Move FnDescriptors to analyzerAleksey Kladov2018-10-311-99/+99
|
* Introduce owned ast nodesAleksey Kladov2018-10-311-1/+1288
| | | | ast::FooNode is an owned 'static counterpart to ast::Foo<'a>
* Complete crate:: pathsAleksey Kladov2018-10-241-0/+4
|
* rename gen-kinds to gen-syntaxAleksey Kladov2018-10-161-1/+1
|
* Cargo FormatJeremy A. Kolb2018-10-161-0/+2
| | | | Run `cargo fmt` and ignore generated files
* Run cargo fixAleksey Kladov2018-10-151-1/+1
|
* Merge #127bors[bot]2018-10-151-0/+18
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/+18
| |
* | 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-111-0/+18
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-111-0/+18
| |
* | Update crates/ra_syntax/src/ast/generated.rsReinier Maas2018-10-101-32/+64
|/ | | | effect of running cargo gen-kinds
* Add `cargo gen-kinds` documentationDaniel McNab2018-10-041-0/+3
|
* rename all thingsAleksey Kladov2018-09-161-0/+2142
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-25 12:36:45 +0000