Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Use more generic public api | Kirill Bulatov | 2020-03-24 | 2 | -21/+21 |
| | |||||
* | Remove the upcast | Kirill Bulatov | 2020-03-24 | 1 | -3/+7 |
| | |||||
* | Auto import macros | Kirill Bulatov | 2020-03-24 | 1 | -12/+19 |
| | |||||
* | update itertools version to 0.9.0 | Josh Mcguigan | 2020-03-23 | 1 | -1/+1 |
| | |||||
* | Merge pull request #3686 from Veetaha/feature/hover-actual-type-params | Aleksey Kladov | 2020-03-23 | 2 | -15/+17 |
|\ | | | | | ra_hir: add more privacy for Type | ||||
| * | ra_hir: add more privacy for Type | veetaha | 2020-03-23 | 2 | -15/+17 |
| | | |||||
* | | Merge pull request #3678 from edwin0cheng/refactor-rename | Aleksey Kladov | 2020-03-23 | 1 | -1/+28 |
|\ \ | | | | | | | Fix rename argument in macro call | ||||
| * | | Fix typo | Edwin Cheng | 2020-03-22 | 1 | -1/+1 |
| | | | | | | | | | Co-Authored-By: Veetaha <[email protected]> | ||||
| * | | Add find_node_at_offset_with_descend | Edwin Cheng | 2020-03-22 | 1 | -1/+28 |
| | | | |||||
* | | | ra_hir: fix typo | veetaha | 2020-03-23 | 1 | -1/+1 |
| | | | |||||
* | | | ra_hir: add more docs | veetaha | 2020-03-23 | 1 | -0/+12 |
| |/ |/| | |||||
* | | ra_hir: migrate some stuff to matches!() | veetaha | 2020-03-22 | 1 | -18/+6 |
|/ | |||||
* | Use `dyn Trait` for working with databse | Aleksey Kladov | 2020-03-16 | 5 | -262/+265 |
| | | | | | | | It improves compile time in `--release` mode quite a bit, it doesn't really slow things down and, conceptually, it seems closer to what we want the physical architecture to look like (we don't want to monomorphise EVERYTHING in a single leaf crate). | ||||
* | Fix completion of HashMap::new | Florian Diebold | 2020-03-13 | 1 | -2/+10 |
| | | | | | | | | | | | | | | | The `ty` function in code_model returned the type with placeholders for type parameters. That's nice for printing, but not good for completion, because placeholders won't unify with anything else: So the type we got for `HashMap` was `HashMap<K, V, T>`, which doesn't unify with `HashMap<?, ?, RandomState>`, so the `new` method wasn't shown. Now we instead return `HashMap<{unknown}, {unknown}, {unknown}>`, which does unify with the impl type. Maybe we should just expose this properly as variables though, i.e. we'd return something like `exists<type, type, type> HashMap<?0, ?1, ?2>` (in Chalk notation). It'll make the API more complicated, but harder to misuse. (And it would handle cases like `type TypeAlias<T> = HashMap<T, T>` more correctly.) | ||||
* | Restore cargo-fmt gating | Aleksey Kladov | 2020-03-13 | 2 | -13/+9 |
| | |||||
* | fix issue 3444 | Josh Mcguigan | 2020-03-13 | 3 | -11/+46 |
| | |||||
* | Simplify | Aleksey Kladov | 2020-03-09 | 1 | -1/+1 |
| | |||||
* | Use `Index` for CrateGraph | Aleksey Kladov | 2020-03-09 | 1 | -5/+4 |
| | |||||
* | Merge #3519 | bors[bot] | 2020-03-09 | 1 | -5/+32 |
|\ | | | | | | | | | | | | | | | 3519: Show mod path on hover r=matklad a=SomeoneToIgnore Closes #1064 Co-authored-by: Kirill Bulatov <[email protected]> | ||||
| * | Less abstract CrateData api | Kirill Bulatov | 2020-03-09 | 1 | -5/+8 |
| | | |||||
| * | Show mod path in hover tooltip | Kirill Bulatov | 2020-03-07 | 1 | -0/+24 |
| | | |||||
* | | Merge #3513 | bors[bot] | 2020-03-09 | 2 | -1/+36 |
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3513: Completion in macros r=matklad a=flodiebold I experimented a bit with completion in macros. It's kind of working, but there are a lot of rough edges. - I'm trying to expand the macro call with the inserted fake token. This requires some hacky additions on the HIR level to be able to do "hypothetical" expansions. There should probably be a nicer API for this, if we want to do it this way. I'm not sure whether it's worth it, because we still can't do a lot if the original macro call didn't expand in nearly the same way. E.g. if we have something like `println!("", x<|>)` the expansions will look the same and everything is fine; but in that case we could maybe have achieved the same result in a simpler way. If we have something like `m!(<|>)` where `m!()` doesn't even expand or expands to something very different, we don't really know what to do anyway. - Relatedly, there are a lot of cases where this doesn't work because either the original call or the hypothetical call doesn't expand. E.g. if we have `m!(x.<|>)` the original token tree doesn't parse as an expression; if we have `m!(match x { <|> })` the hypothetical token tree doesn't parse. It would be nice if we could have better error recovery in these cases. Co-authored-by: Florian Diebold <[email protected]> | ||||
| * | | Move hypothetical expansion to hir_expand | Florian Diebold | 2020-03-08 | 1 | -21/+3 |
| | | | |||||
| * | | Try to complete within macros | Florian Diebold | 2020-03-07 | 2 | -2/+55 |
| |/ | |||||
* | | Handle visibility for assoc item path completion as well | Florian Diebold | 2020-03-08 | 1 | -8/+40 |
| | | |||||
* | | Handle visibility for path completion (not in all cases yet) | Florian Diebold | 2020-03-08 | 1 | -1/+11 |
| | | |||||
* | | Handle visibility in method call completion | Florian Diebold | 2020-03-07 | 1 | -0/+8 |
|/ | |||||
* | Normalize waiting queries names | Aleksey Kladov | 2020-03-06 | 1 | -5/+5 |
| | |||||
* | Don't reuse the Chalk solver | Florian Diebold | 2020-03-06 | 1 | -2/+1 |
| | | | | | This slows down analysis-stats a bit (~5% in my measurement), but improves incremental checking a lot because we can reuse trait solve results. | ||||
* | Source map returns a result | Aleksey Kladov | 2020-03-06 | 1 | -2/+2 |
| | | | | cc #2236 | ||||
* | Move PathResolution | Aleksey Kladov | 2020-03-05 | 3 | -19/+18 |
| | |||||
* | Remove dead code | Aleksey Kladov | 2020-03-05 | 1 | -7/+1 |
| | |||||
* | Minor cleanup | Aleksey Kladov | 2020-03-04 | 1 | -16/+14 |
| | |||||
* | Remove old find refs infra | Aleksey Kladov | 2020-03-04 | 2 | -41/+2 |
| | |||||
* | Refactor reference search a bit | Aleksey Kladov | 2020-03-03 | 1 | -1/+11 |
| | |||||
* | More principled approach for gotodef for field shorhand | Aleksey Kladov | 2020-03-02 | 2 | -10/+24 |
| | | | | | Callers can now decide for themselves if they should prefer field or local definition. By default, it's the local. | ||||
* | Rename ast::ImplBlock -> ast::ImplDef | Aleksey Kladov | 2020-02-29 | 7 | -30/+30 |
| | |||||
* | Handle tuple fields as well | Aleksey Kladov | 2020-02-29 | 2 | -1/+7 |
| | |||||
* | Minor | Aleksey Kladov | 2020-02-29 | 2 | -5/+4 |
| | |||||
* | Simplify SourceBinder | Aleksey Kladov | 2020-02-29 | 6 | -349/+321 |
| | |||||
* | Small cleanup | Aleksey Kladov | 2020-02-29 | 1 | -9/+15 |
| | |||||
* | Reduce visibility | Aleksey Kladov | 2020-02-28 | 2 | -3/+3 |
| | |||||
* | Merge #3367 | bors[bot] | 2020-02-28 | 2 | -7/+32 |
|\ | | | | | | | | | | | | | | | | | | | | | 3367: Fix highlighting of const patterns r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]> | ||||
| * | Fix highlighting of const patterns | Aleksey Kladov | 2020-02-28 | 2 | -7/+32 |
| | | |||||
* | | Simpilfy origin_range logic | Edwin Cheng | 2020-02-28 | 1 | -38/+27 |
|/ | |||||
* | Use text_range::extend_to | Edwin Cheng | 2020-02-27 | 1 | -10/+3 |
| | |||||
* | Skip trival token in original_range | Edwin Cheng | 2020-02-26 | 1 | -5/+7 |
| | |||||
* | Remove duplicate comment | Edwin Cheng | 2020-02-26 | 1 | -1/+0 |
| | |||||
* | Add recursive support in original_range | Edwin Cheng | 2020-02-26 | 1 | -14/+37 |
| | |||||
* | Remove dead code | Aleksey Kladov | 2020-02-26 | 2 | -25/+9 |
| |