aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/src/grammar.ron
Commit message (Collapse)AuthorAgeFilesLines
* Revert "eagarly clean astd maps"Aleksey Kladov2019-05-041-1/+1
| | | | | | This reverts commit 6c63a59425e256ce46d058807b64149297231982. This causes massive slowdowns: looks like we accidentally have some source-depndent
* eagarly clean astd mapsAleksey Kladov2019-05-041-1/+1
|
* Add default type param in TypeParam NodeEdwin Cheng2019-05-031-1/+1
|
* Merge #1154bors[bot]2019-04-201-1/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1154: Initial support for lang items (and str completion) r=flodiebold a=marcogroppo This PR adds partial support for lang items. For now, the only supported lang items are the ones that target an impl block. Lang items are now resolved during type inference - this means that `str` completion now works. Fixes #1139. (thanks Florian Diebold for the help!) Co-authored-by: Marco Groppo <[email protected]>
| * Initial support for lang items.Marco Groppo2019-04-191-1/+1
| |
* | Add MacroItems and MacroStmts in grammer.ronEdwin Cheng2019-04-181-0/+15
|/
* Add L_DOLLAR and R_DOLLAREdwin Cheng2019-04-111-0/+2
|
* Merge #1076bors[bot]2019-04-021-0/+2
|\ | | | | | | | | | | | | | | | | 1076: Const body inference r=flodiebold a=Lapz This is the second part of #887. I've added type inference on const bodies and introduced the DefWithBody containing Function, Const and Static. I want to add tests but im unsure on how I would go about testing that completions work. Co-authored-by: Lenard Pratt <[email protected]>
| * Added const bodies and static body to the astLenard Pratt2019-04-021-2/+2
| | | | | | | | | | | | and added inference the inference test reduce code duplication
| * Added defWithBodyLenard Pratt2019-03-301-0/+2
| |
* | Merge #1084bors[bot]2019-04-011-1/+0
|\ \ | | | | | | | | | | | | | | | | | | | | | 1084: remove dead code r=matklad a=matklad Co-authored-by: Aleksey Kladov <[email protected]>
| * | remove dead codeAleksey Kladov2019-04-011-1/+0
| | |
* | | intelligently add parens when inlining local varaiblesgfreezy2019-04-011-0/+1
|/ /
* | switch to new rowanAleksey Kladov2019-04-011-33/+2
| |
* | Add WherePred to allow predicate access in WhereClauseVille Penttinen2019-03-311-1/+14
| | | | | | | | | | This also unifies parsing of WHERE_PRED bounds, now Lifetime bounds will also be parsed using TYPE_BOUND_LIST
* | Add trait ast::TypeBoundsOwnerVille Penttinen2019-03-311-5/+10
| |
* | Add new TYPE_BOUND_LIST and TYPE_BOUND syntax kindsVille Penttinen2019-03-301-0/+13
|/ | | | | | These are now used when parsing type bounds. In addition parsing paths inside a bound now does not recursively parse paths, rather they are treated as separate bounds, separated by +.
* Basics for trait method resolutionFlorian Diebold2019-03-251-1/+4
|
* add name resolution from the old implAleksey Kladov2019-03-171-1/+1
| | | | unlike the old impl, this also handles macro imports across crates
* Add async keywordCaio2019-03-091-0/+1
|
* Remove `TypeRef` from item opts which implement TypeAscriptionOwnerVille Penttinen2019-02-271-6/+11
|
* Add new trait TypeAscriptionOwnerVille Penttinen2019-02-261-9/+24
| | | | | This trait should be implemented for nodes which have an ascribed type, e.g. thing : Type. Such as let, const, static, param, named struct fields.
* rename type to type_alias in the AST as wellAleksey Kladov2019-02-251-4/+4
|
* Enable parsing attributes for generic lifetimes and type parametersVille Penttinen2019-02-171-2/+5
|
* Enable parsing of attributes inside a match blockVille Penttinen2019-02-171-1/+3
| | | | | | | We allow invalid inner attributes to be parsed, e.g. inner attributes that are not directly after the opening brace of the match block. Instead we run validation on `MatchArmList` to allow better reporting of errors.
* Handle generic args for method callsFlorian Diebold2019-02-161-1/+1
|
* Add generic params to impl blocksFlorian Diebold2019-02-161-1/+1
|
* Import the preludeFlorian Diebold2019-02-131-1/+2
|
* make macro a NameOwnerAleksey Kladov2019-02-111-1/+4
|
* Fix handling of literal patternsFlorian Diebold2019-02-091-0/+3
| | | | | Wrap them in a LiteralPat node so they can be distinguished from literal expressions.
* Fill deprecation for LSPkjeremy2019-02-051-1/+1
|
* Add AST for extern crateFlorian Diebold2019-02-041-1/+3
| | | | Also change it to parse the crate name as a NAME_REF, not a NAME.
* Pass aliases to ImportDataFlorian Diebold2019-02-011-1/+4
|
* convert punts and literalsAleksey Kladov2019-01-311-6/+8
|
* Merge #692bors[bot]2019-01-311-0/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 692: [WIP] Correctly parse attributes r=matklad a=DJMcNab Reference - https://doc.rust-lang.org/reference/attributes.html This fixes/investigates inner attributes for: - [x] `impl` blocks - [x] `extern` blocks - [x] `fn`s (fixes #689) - [x] `mod`s (already supported) - [x] 'block expressions' (the long text just describes all 'blocks' used as statements) This also investigates/fixes outer attributes for: - [ ] 'most statements' (see also: #685, https://doc.rust-lang.org/reference/expressions.html#expression-attributes) - [x] Enum variants, Struct and Union fields (Fixed in #507) - [ ] 'Match expression arms' (@matklad can you provide a test case which explains what this means?) - [ ] 'Generic lifetime or type parameters' - [ ] 'Elements of array expressions, tuple expressions, call expressions, tuple-style struct and enum variant expressions' - [ ] 'The tail expression of block expressions' Co-authored-by: DJMcNab <[email protected]>
| * Parse and validate attributes in blocksDJMcNab2019-01-281-0/+3
| |
* | Infer type of match guardMarcus Klaas de Vries2019-01-281-1/+1
|/
* rename POS_FIELD -> POS_FIELD_DEFAleksey Kladov2019-01-251-4/+4
| | | | to match NAMED_FIELD_DEF
* Add docs to struct fieldsJeremy A. Kolb2019-01-251-1/+1
|
* Merge #630bors[bot]2019-01-251-21/+30
|\ | | | | | | | | | | | | | | | | | | | | | | 630: Fill in DocumentSymbol::detail r=matklad a=hban Closes: #516 I just pulled type text from the syntax node and "formatted" is bit. VS Code can't really handle multi-line symbol detail (it's will crop it when rendering), so that formatting will just collapse all white-space to singe space. It isn't pretty, but maybe there's a better way. Issue also mentions "need to be done for `NavigationTarget` to `SymbolInformation`", but `SymbolInformation` doesn't have detail field on it? Co-authored-by: Hrvoje Ban <[email protected]>
| * Fill in DocumentSymbol::detailHrvoje Ban2019-01-241-21/+30
| |
* | Migrate trait & type to new idsAleksey Kladov2019-01-241-2/+2
|/
* Make EnumVariant a DocCommentsOwnerJeremy A. Kolb2019-01-231-1/+1
|
* Add AST/HIR for type args in path segmentsFlorian Diebold2019-01-191-1/+9
|
* Change parsing of struct field patternsMarcus Klaas de Vries2019-01-191-1/+6
|
* Move parsing of field pattern lists to the parser (where it belongs)Marcus Klaas de Vries2019-01-191-1/+6
|
* Add initial (flawed) implementation of binding annotationsMarcus Klaas de Vries2019-01-191-1/+4
|
* Create struct patterns up to the hir levelMarcus Klaas de Vries2019-01-191-3/+2
|
* Add additional pattern variantsMarcus Klaas de Vries2019-01-191-2/+2
|
* Update ARRAY_EXPR grammarHirokazu Hata2019-01-161-1/+3
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-30 16:04:51 +0000