aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax
Commit message (Collapse)AuthorAgeFilesLines
* several highlighting cleanupsAleksey Kladov2019-07-191-0/+11
| | | | | | * make stuff more type-safe by using `BindPat` instead of just `Pat` * don't add `mut` into binding hash * reset shadow counter when we enter a function
* switch to the upstream rowanAleksey Kladov2019-07-191-1/+1
|
* migrate ra_assists to the new ASTAleksey Kladov2019-07-191-1/+1
|
* migrate ra_hir to the new rowanAleksey Kladov2019-07-191-1/+1
|
* migrate ra_syntax to the new rowan APIAleksey Kladov2019-07-1918-2347/+1183
|
* use Parse in mbeAleksey Kladov2019-07-182-6/+13
|
* make Parse genericAleksey Kladov2019-07-181-14/+33
|
* cleanup importsAleksey Kladov2019-07-181-1/+1
|
* highlight mutable variables differentlyEkaterina Babshukova2019-07-181-1/+1
|
* use more correct phantom types for ptrsAleksey Kladov2019-07-181-1/+1
|
* make Parse fields privateAleksey Kladov2019-07-122-4/+12
| | | | this is in preparation for the new rowan API
* Make clippy a bit happierPascal Hertleif2019-07-101-0/+4
| | | | | Random drive-by fix. I honestly blame rust-analyzer itself on this, because I set its watch mode to use `cargo clippy` :shrug:
* Resolve a FIXMEPascal Hertleif2019-07-101-3/+1
| | | | Now that we are using a newer smol_str release this can be simplified :)
* Remove unused dependenciesShotaro Yamada2019-07-081-3/+0
|
* Constify KnownName'sMuhammad Mominul Huque2019-07-071-1/+1
|
* Clippy changesJeremy Kolb2019-07-051-1/+1
|
* Some clippy fixes for 1.36Jeremy Kolb2019-07-045-6/+6
|
* allow rustfmt to reorder importsAleksey Kladov2019-07-0423-81/+72
| | | | | | This wasn't a right decision in the first place, the feature flag was broken in the last rustfmt release, and syntax highlighting of imports is more important anyway
* Remove parse error on array initializer attributesRyan Cumming2019-06-302-65/+0
| | | | | This is actually allowed by the `rustc` parser but most attributes will fail later due to attributes on expressions being experimental.
* Support attributes on array membersRyan Cumming2019-06-306-0/+177
| | | | | | | | | | | | Array members are allow to have attributes such as `#[cfg]`. This is a bit tricky as we don't know if the first expression is an initializer or a member until we encounter a `;`. This reuses a trick from `stmt` where we remember if we saw an attribute and then raise an error if the first expression ends up being an initializer. This isn't perfect as the error isn't correctly located on the attribute or initializer; it ends up immediately after the `;`.
* fixed #1384zjy2019-06-282-0/+70
|
* Merge #1415bors[bot]2019-06-244-0/+121
|\ | | | | | | | | | | | | | | | | 1415: fix: specialization r=matklad a=csmoe Closes #1402 r? @matklad Co-authored-by: csmoe <[email protected]>
| * fix: specialization(with blindly parsing)csmoe2019-06-194-0/+121
| | | | | | | | Change-Id: Ic5d2767e8781568d76d4d0013cd6081e95ae8a95
* | fix: box_patterncsmoe2019-06-195-6/+69
| | | | | | | | Change-Id: I45a856d74fb616d3bce33050f9e69d327186bd59
* | fix: box_syntax(#1412)csmoe2019-06-181-0/+3
|/ | | | Change-Id: I6e20e0163fa545de37226c1561b3b7103615626c
* Fix formattingShotaro Yamada2019-06-151-7/+3
|
* Skip attrs in `Literal::token`Shotaro Yamada2019-06-151-2/+17
|
* Get rid of failure: ra_batch ra_cliMuhammad Mominul Huque2019-06-151-1/+1
|
* fix: support existential typecsmoe2019-06-125-3/+36
|
* fix: never type with bindingcsmoe2019-06-072-6/+38
| | | | Change-Id: I14e1bc628b9d2dfdb1f40de3d3707f4e872767f2
* [#1083] Try block syntax: fix testsAndrey Tkachenko2019-06-064-37/+34
|
* [#1083] Try block syntaxAndrey Tkachenko2019-06-065-0/+86
|
* fix: clean up warningscsmoe2019-06-061-3/+3
| | | | Change-Id: I91a468f6e846ac28574825b8ee7aa02fbff68f63
* Fix clippy::or_fun_callAlan Du2019-06-041-1/+1
|
* Fix clippy::single_char_patternAlan Du2019-06-041-1/+1
|
* :arrow_up: parking_lotAleksey Kladov2019-05-301-1/+0
|
* flip Into to FromAleksey Kladov2019-05-291-6/+6
|
* show error offsets in testsAleksey Kladov2019-05-2946-290/+299
|
* remove old parsing methodsAleksey Kladov2019-05-287-62/+54
|
* update test dataAleksey Kladov2019-05-2845-289/+290
|
* update testsAleksey Kladov2019-05-284-47/+36
|
* drop error from SOurceFile constructorAleksey Kladov2019-05-282-5/+5
|
* return errors from tree builderAleksey Kladov2019-05-281-3/+3
|
* drop errors from SyntaxNodeAleksey Kladov2019-05-282-9/+6
|
* add ParseAleksey Kladov2019-05-281-2/+26
|
* Make rainbows optionalPascal Hertleif2019-05-271-1/+2
|
* More clever highlighting, incl draft for structsPascal Hertleif2019-05-271-4/+0
|
* Hash based on binding name and shadow counterPascal Hertleif2019-05-271-1/+6
|
* Semantic highlighting spikePascal Hertleif2019-05-271-0/+4
| | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?
* Change TokenSource to iteration basedEdwin Cheng2019-05-253-17/+38
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 12:03:47 +0000