Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Validate string literals | Adolfo Ochagavía | 2018-11-09 | 9 | -274/+621 |
| | |||||
* | Complete paths in use trees | Aleksey Kladov | 2018-11-07 | 1 | -0/+9 |
| | |||||
* | rename ROOT -> SOURCE_FILE | Aleksey Kladov | 2018-11-07 | 183 | -232/+231 |
| | |||||
* | Rename File -> SourceFileNode | Aleksey Kladov | 2018-11-07 | 5 | -24/+24 |
| | |||||
* | Add some more DocCommentsOwner | Jeremy A. Kolb | 2018-11-07 | 2 | -2/+14 |
| | |||||
* | Merge #207 | bors[bot] | 2018-11-07 | 7 | -13/+234 |
|\ | | | | | | | | | | | | | | | 207: Finish implementing char validation r=aochagavia a=aochagavia The only thing missing right now are good integration tests (and maybe more descriptive error messages) Co-authored-by: Adolfo Ochagavía <[email protected]> | ||||
| * | Fix backslash escape | Adolfo Ochagavía | 2018-11-07 | 1 | -2/+4 |
| | | |||||
| * | Use ArrayString instead of hand rolled data structure | Adolfo Ochagavía | 2018-11-07 | 4 | -39/+5 |
| | | |||||
| * | cargo format | Adolfo Ochagavía | 2018-11-07 | 2 | -30/+39 |
| | | |||||
| * | Add lots of tests | Adolfo Ochagavía | 2018-11-07 | 3 | -6/+125 |
| | | |||||
| * | Store hex digits in a stack-allocated buffer | Adolfo Ochagavía | 2018-11-07 | 2 | -5/+45 |
| | | |||||
| * | Finish implementing char validation | Adolfo Ochagavía | 2018-11-06 | 3 | -8/+93 |
| | | |||||
* | | ra_syntax::File is just RootNode | Aleksey Kladov | 2018-11-06 | 4 | -206/+969 |
| | | |||||
* | | Add a pinch of comments | Aleksey Kladov | 2018-11-06 | 3 | -0/+16 |
| | | |||||
* | | Generalize Owned nodes | Aleksey Kladov | 2018-11-06 | 2 | -1806/+1237 |
| | | |||||
* | | grammar: fix where clause parsing | Aleksey Kladov | 2018-11-06 | 3 | -1/+35 |
| | | | | | | | | closes #205 | ||||
* | | upstream basic tree algorithms to rowan | Aleksey Kladov | 2018-11-06 | 3 | -107/+10 |
|/ | |||||
* | Merge #188 | bors[bot] | 2018-11-05 | 10 | -66/+183 |
|\ | | | | | | | | | | | | | | | | | 188: Introduce `SyntaxErrorKind` and `TextRange` to `SyntaxError` r=matklad a=aochagavia Co-authored-by: Adolfo Ochagavía <[email protected]> Co-authored-by: Adolfo Ochagavía <[email protected]> | ||||
| * | cargo format | Adolfo Ochagavía | 2018-11-05 | 2 | -5/+9 |
| | | |||||
| * | Introduce Location and make SyntaxError fields private | Adolfo Ochagavía | 2018-11-05 | 9 | -50/+72 |
| | | |||||
| * | Introduce SyntaxErrorKind and TextRange in SyntaxError | Adolfo Ochagavía | 2018-11-04 | 9 | -62/+153 |
| | | |||||
* | | bring back testutils | Aleksey Kladov | 2018-11-05 | 1 | -1/+1 |
| | | |||||
* | | add description | Aleksey Kladov | 2018-11-05 | 1 | -1/+3 |
| | | |||||
* | | Switch ra_syntax to 2015 edition | Aleksey Kladov | 2018-11-05 | 2 | -1/+4 |
| | | |||||
* | | reduce code duplication | Aleksey Kladov | 2018-11-05 | 2 | -21/+19 |
| | | |||||
* | | grammar: for predicates in where | Aleksey Kladov | 2018-11-05 | 4 | -35/+129 |
|/ | | | | closes #191 | ||||
* | Add character literal parsing and validation | Adolfo Ochagavía | 2018-11-04 | 6 | -2/+397 |
| | |||||
* | Don't order import alphabetical | Aleksey Kladov | 2018-11-01 | 1 | -1/+1 |
| | | | | | alphabetical ordering is no more consistent, and much less useful then the ordering which arises naturally when you add import. | ||||
* | Use From to get an owned AST | Aleksey Kladov | 2018-11-01 | 2 | -400/+700 |
| | |||||
* | Remove DOC_COMMENT | Jeremy A. Kolb | 2018-10-31 | 4 | -5/+2 |
| | | | | Closes #166 | ||||
* | Reformat all | Aleksey Kladov | 2018-10-31 | 4 | -13/+16 |
| | |||||
* | `ast::DocCommentsOwner` which represents a documentation comment owner | Jeremy A. Kolb | 2018-10-31 | 3 | -0/+20 |
| | |||||
* | Move FnDescriptors to analyzer | Aleksey Kladov | 2018-10-31 | 2 | -100/+100 |
| | |||||
* | Introduce owned ast nodes | Aleksey Kladov | 2018-10-31 | 2 | -2/+1303 |
| | | | | ast::FooNode is an owned 'static counterpart to ast::Foo<'a> | ||||
* | switch to TextRange::subrange | Aleksey Kladov | 2018-10-30 | 2 | -6/+2 |
| | |||||
* | introduce syntax-ptr | Aleksey Kladov | 2018-10-30 | 1 | -0/+1 |
| | |||||
* | Complete crate:: paths | Aleksey Kladov | 2018-10-24 | 3 | -1/+36 |
| | |||||
* | Fix function calls | Alan Du | 2018-10-18 | 3 | -3/+3 |
| | |||||
* | clippy: type_complexity | Alan Du | 2018-10-18 | 1 | -4/+5 |
| | |||||
* | Remove Copy trait on LeafAtOffset | Alan Du | 2018-10-18 | 1 | -1/+1 |
| | | | | | | | Because it's a stateful iterator, it's easier to explicitly clone it when necesary. Fixes clippy:clone_on_copy | ||||
* | clippy: Use if lets and remove redundant returns | Alan Du | 2018-10-18 | 6 | -16/+12 |
| | |||||
* | Update rowan | Aleksey Kladov | 2018-10-17 | 6 | -39/+16 |
| | |||||
* | rename gen-kinds to gen-syntax | Aleksey Kladov | 2018-10-16 | 5 | -5/+5 |
| | |||||
* | Cargo Format | Jeremy A. Kolb | 2018-10-16 | 31 | -391/+490 |
| | | | | Run `cargo fmt` and ignore generated files | ||||
* | start salsa migration | Aleksey Kladov | 2018-10-15 | 1 | -1/+1 |
| | |||||
* | regenerate | Aleksey Kladov | 2018-10-15 | 1 | -1/+1 |
| | |||||
* | Parse crate paths in expressions | Aleksey Kladov | 2018-10-15 | 3 | -1/+45 |
| | |||||
* | switch base crates to 2018 | Aleksey Kladov | 2018-10-15 | 1 | -0/+1 |
| | |||||
* | Run cargo fix | Aleksey Kladov | 2018-10-15 | 24 | -44/+44 |
| | |||||
* | Merge #127 | bors[bot] | 2018-10-15 | 3 | -3/+44 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]> |