Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | feat: add attributes support on struct fields and method #3870 | Benjamin Coenen | 2020-04-09 | 3 | -83/+151 | |
|\ | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]> | |||||
| * | match checking add additional test for match checking tuple with missing pattern | Josh Mcguigan | 2020-04-08 | 1 | -0/+14 | |
| | | ||||||
| * | fix panic in match checking when tuple enum missing pattern | Josh Mcguigan | 2020-04-08 | 1 | -15/+45 | |
| | | ||||||
| * | Move computation of missing fields into hir | Aleksey Kladov | 2020-04-07 | 1 | -67/+91 | |
| | | ||||||
* | | feat: add attributes support on struct fields and method #3870 | Benjamin Coenen | 2020-04-08 | 2 | -12/+6 | |
| | | | | | | | | Signed-off-by: Benjamin Coenen <[email protected]> | |||||
* | | Merge branch 'master' of github.com:rust-analyzer/rust-analyzer | Benjamin Coenen | 2020-04-07 | 11 | -11/+1579 | |
|\| | ||||||
| * | add fixme to use type checker rather than manually comparing types | Josh Mcguigan | 2020-04-07 | 1 | -0/+7 | |
| | | ||||||
| * | PR feedback implementation | Josh Mcguigan | 2020-04-07 | 1 | -94/+331 | |
| | | ||||||
| * | missing match arms diagnostic change source to match expression | Josh Mcguigan | 2020-04-07 | 3 | -3/+7 | |
| | | ||||||
| * | handle match auto-deref | Josh Mcguigan | 2020-04-07 | 2 | -1/+45 | |
| | | ||||||
| * | improving documentation | Josh Mcguigan | 2020-04-07 | 1 | -16/+64 | |
| | | ||||||
| * | handle non matching enum pattern types | Josh Mcguigan | 2020-04-07 | 2 | -41/+57 | |
| | | ||||||
| * | remove panics | Josh Mcguigan | 2020-04-07 | 2 | -66/+214 | |
| | | ||||||
| * | missing match arms diagnostic | Josh Mcguigan | 2020-04-07 | 9 | -9/+1037 | |
| | | ||||||
| * | Fix Chalk panic | Florian Diebold | 2020-04-06 | 3 | -2/+33 | |
| | | | | | | | | | | Fixes #3865. Basically I forgot to shift 'back' when we got `dyn Trait`s back from Chalk, so after going through Chalk a few times, the panic happened. | |||||
| * | Check for eprintln on CI | Aleksey Kladov | 2020-04-06 | 1 | -0/+5 | |
| | | ||||||
* | | feat: add attributes support on struct fields #3870 | Benjamin Coenen | 2020-04-07 | 2 | -3/+38 | |
|/ | | | | Signed-off-by: Benjamin Coenen <[email protected]> | |||||
* | Use log info in trait_solve_query | Edwin Cheng | 2020-04-06 | 1 | -1/+1 | |
| | ||||||
* | Merge #3744 | bors[bot] | 2020-04-06 | 11 | -136/+294 | |
|\ | | | | | | | | | | | | | | | | | 3744: Upgrade Chalk r=matklad a=flodiebold Co-authored-by: Florian Diebold <[email protected]> Co-authored-by: Florian Diebold <[email protected]> | |||||
| * | Upgrade Chalk again | Florian Diebold | 2020-04-05 | 11 | -109/+192 | |
| | | | | | | | | | | | | | | The big change here is counting binders, not variables (https://github.com/rust-lang/chalk/pull/360). We have to adapt to the same scheme for our `Ty::Bound`. It's mostly fine though, even makes some things more clear. | |||||
| * | Upgrade Chalk | Florian Diebold | 2020-04-05 | 3 | -30/+105 | |
| | | ||||||
* | | Hide unit fn return types | Laurențiu Nicola | 2020-04-05 | 5 | -20/+28 | |
|/ | ||||||
* | Fix inference of function pointer return types | Laurențiu Nicola | 2020-04-05 | 1 | -0/+26 | |
| | ||||||
* | Macro patterns are not confused with expressions. | Aleksey Kladov | 2020-04-03 | 1 | -2/+29 | |
| | | | | | | | | | | | We treat macro calls as expressions (there's appropriate Into impl), which causes problem if there's expresison and non-expression macro in the same node (like in the match arm). We fix this problem by nesting macor patterns into another node (the same way we nest path into PathExpr or PathPat). Ideally, we probably should add a similar nesting for macro expressions, but that needs some careful thinking about macros in blocks: `{ am_i_expression!() }`. | |||||
* | Add inference for literal and range patterns | Florian Diebold | 2020-04-01 | 5 | -3/+104 | |
| | ||||||
* | Simplify | veetaha | 2020-03-31 | 1 | -16/+13 | |
| | ||||||
* | Simplify | veetaha | 2020-03-28 | 1 | -11/+4 | |
| | ||||||
* | Remove some unwraps | Aleksey Kladov | 2020-03-28 | 2 | -18/+16 | |
| | ||||||
* | Nice string formatting | Aleksey Kladov | 2020-03-28 | 2 | -1/+4 | |
| | ||||||
* | Cleanup memory usage stats | Aleksey Kladov | 2020-03-25 | 1 | -0/+1 | |
| | ||||||
* | Remove collect proc_macro definitions | Edwin Cheng | 2020-03-25 | 1 | -6/+2 | |
| | ||||||
* | Fix trailling whitespace | Edwin Cheng | 2020-03-25 | 1 | -1/+1 | |
| | ||||||
* | Add basic custom derive lowering | Edwin Cheng | 2020-03-25 | 1 | -0/+23 | |
| | ||||||
* | Merge #3679 | bors[bot] | 2020-03-22 | 1 | -8/+8 | |
|\ | | | | | | | | | | | | | | | 3679: Some miniscule refactorings r=matklad a=Veetaha Co-authored-by: veetaha <[email protected]> | |||||
| * | ra_hir_ty: fix formatting | veetaha | 2020-03-22 | 1 | -8/+8 | |
| | | ||||||
* | | Move test to hir_ty | Edwin Cheng | 2020-03-21 | 1 | -0/+31 | |
|/ | ||||||
* | Make MBE expansion more resilient (WIP) | Florian Diebold | 2020-03-16 | 1 | -4/+4 | |
| | ||||||
* | Use `dyn Trait` for working with databse | Aleksey Kladov | 2020-03-16 | 18 | -346/+337 | |
| | | | | | | | 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). | |||||
* | Support local macro_rules | Edwin Cheng | 2020-03-14 | 1 | -0/+20 | |
| | ||||||
* | Merge #3549 | bors[bot] | 2020-03-11 | 2 | -0/+27 | |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3549: Implement env! macro r=matklad a=edwin0cheng This PR implements `env!` macro by adding following things: 1. Added `additional_outdirs` settings in vscode. (naming to be bikeshed) 2. Added `ExternSourceId` which is a wrapping for SourceRootId but only used in extern sources. It is because `OUT_DIR` is not belonged to any crate and we have to access it behind an `AstDatabase`. 3. This PR does not implement the `OUT_DIR` parsing from `cargo check`. I don't have general design about this, @kiljacken could we reuse some cargo watch code for that ? ~~Block on [#3536]~~ PS: After this PR , we (kind of) completed the `include!(concat!(env!('OUT_DIR'), "foo.rs")` macro call combo. [Exodia Obliterate!](https://www.youtube.com/watch?v=RfqNH3FoGi0) Co-authored-by: Edwin Cheng <[email protected]> | |||||
| * | Add and fix tests | Edwin Cheng | 2020-03-10 | 1 | -0/+20 | |
| | | ||||||
| * | Add resolve_extern_path in DB | Edwin Cheng | 2020-03-10 | 1 | -0/+7 | |
| | | ||||||
* | | Fix completion with a partially unknown type | Florian Diebold | 2020-03-10 | 1 | -3/+25 | |
|/ | | | | | | | | | | | | | | To test whether the receiver type matches for the impl, we unify the given self type (in this case `HashSet<{unknown}>`) with the self type of the impl (`HashSet<?0>`), but if the given self type contains Unknowns, they won't be unified with the variables in those places. So we got a receiver type that was different from the expected one, and concluded the impl doesn't match. The fix is slightly hacky; if after the unification, our variables are still there, we make them fall back to Unknown. This does make some sense though, since we don't want to 'leak' the variables. Fixes #3547. | |||||
* | Updates insta to 0.15.0 and bumps console to 0.10.0 | kjeremy | 2020-03-09 | 1 | -1/+1 | |
| | ||||||
* | Use `Index` for CrateGraph | Aleksey Kladov | 2020-03-09 | 1 | -1/+1 | |
| | ||||||
* | Less abstract CrateData api | Kirill Bulatov | 2020-03-09 | 1 | -1/+1 | |
| | ||||||
* | Prevent include! macro include itself | Edwin Cheng | 2020-03-07 | 1 | -0/+18 | |
| | ||||||
* | Use a not so dummy implementation of env macro | Edwin Cheng | 2020-03-07 | 1 | -0/+27 | |
| | ||||||
* | Normalize waiting queries names | Aleksey Kladov | 2020-03-06 | 3 | -10/+10 | |
| | ||||||
* | Don't reuse the Chalk solver | Florian Diebold | 2020-03-06 | 2 | -92/+28 | |
| | | | | | This slows down analysis-stats a bit (~5% in my measurement), but improves incremental checking a lot because we can reuse trait solve results. |