Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Simplify Arena to use a generic index | Aleksey Kladov | 2020-03-19 | 1 | -13/+5 |
| | |||||
* | ra_hir_def: remove dat fixme | veetaha | 2020-03-18 | 1 | -1/+0 |
| | |||||
* | Use `dyn Trait` for working with databse | Aleksey Kladov | 2020-03-16 | 1 | -24/+24 |
| | | | | | | | 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). | ||||
* | Implement concat macro | Edwin Cheng | 2020-03-03 | 1 | -5/+18 |
| | |||||
* | Rename ast::ImplBlock -> ast::ImplDef | Aleksey Kladov | 2020-02-29 | 1 | -1/+1 |
| | |||||
* | More manual clippy fixes | Kirill Bulatov | 2020-02-18 | 1 | -2/+2 |
| | |||||
* | Introduce AsMacroCall trait | Edwin Cheng | 2020-02-17 | 1 | -1/+62 |
| | |||||
* | Introduce SourceBinder | Aleksey Kladov | 2020-01-15 | 1 | -1/+1 |
| | |||||
* | find_path WIP | Florian Diebold | 2020-01-11 | 1 | -0/+1 |
| | |||||
* | Remove visibility query, instead add struct field visibility to data | Florian Diebold | 2019-12-26 | 1 | -23/+0 |
| | | | | | Methods should be handled the same, and for items the visibility will be in the def map. | ||||
* | Add infrastructure for visibility on syntax and hir_def level | Florian Diebold | 2019-12-26 | 1 | -0/+25 |
| | |||||
* | Move LocalImportId | Aleksey Kladov | 2019-12-21 | 1 | -4/+0 |
| | |||||
* | Remove imports from hir | Aleksey Kladov | 2019-12-21 | 1 | -1/+1 |
| | |||||
* | Revert "Merge #2629" | Aleksey Kladov | 2019-12-21 | 1 | -0/+4 |
| | | | | | This reverts commit cdc9d682b066b110e0a44e5f8f1c574b38c16ba9, reversing changes made to 90ef070db3dce0a7acb9cd11d0b0d72de13c9d79. | ||||
* | Privatize LocalImportID | Aleksey Kladov | 2019-12-21 | 1 | -4/+0 |
| | |||||
* | Merge #2624 | bors[bot] | 2019-12-20 | 1 | -0/+1 |
|\ | | | | | | | | | | | | | | | 2624: Separate module item from module scope r=matklad a=matklad bors r+ Co-authored-by: Aleksey Kladov <[email protected]> | ||||
| * | Add item_scope module | Aleksey Kladov | 2019-12-20 | 1 | -0/+1 |
| | | |||||
* | | Add support macros in impl blocks | Edwin Cheng | 2019-12-20 | 1 | -0/+1 |
|/ | |||||
* | Reduce copy-paste some more | Aleksey Kladov | 2019-12-20 | 1 | -13/+1 |
| | |||||
* | Use generic ItemLoc for impls | Aleksey Kladov | 2019-12-20 | 1 | -23/+4 |
| | |||||
* | Remove more copy-paste | Aleksey Kladov | 2019-12-20 | 1 | -121/+29 |
| | |||||
* | Remove more copy-paste | Aleksey Kladov | 2019-12-20 | 1 | -57/+30 |
| | |||||
* | Support for nested traits | Aleksey Kladov | 2019-12-20 | 1 | -3/+3 |
| | |||||
* | Support for nested statics, consts and type aliases | Aleksey Kladov | 2019-12-20 | 1 | -3/+3 |
| | |||||
* | Support for nested ADT | Aleksey Kladov | 2019-12-20 | 1 | -4/+5 |
| | |||||
* | Introduce `ContainerId` | Aleksey Kladov | 2019-12-20 | 1 | -4/+18 |
| | |||||
* | Rename ContainerId -> AssocContainerId | Aleksey Kladov | 2019-12-20 | 1 | -9/+9 |
| | |||||
* | Add body as a possible container for items | Aleksey Kladov | 2019-12-19 | 1 | -12/+12 |
| | |||||
* | Remove old location infra | Aleksey Kladov | 2019-12-12 | 1 | -61/+4 |
| | |||||
* | Move enum&union to new loc | Aleksey Kladov | 2019-12-12 | 1 | -13/+37 |
| | |||||
* | Move structs to new loc | Aleksey Kladov | 2019-12-12 | 1 | -6/+18 |
| | |||||
* | Move traits to the new loc | Aleksey Kladov | 2019-12-12 | 1 | -9/+21 |
| | |||||
* | Switch to the new location for impls | Aleksey Kladov | 2019-12-12 | 1 | -9/+21 |
| | |||||
* | Rename GenericParam -> TypeParam | Aleksey Kladov | 2019-12-07 | 1 | -4/+4 |
| | | | | We don't have LifetimeParam yet, but they are planned! | ||||
* | Classify name works for TypeParams | Aleksey Kladov | 2019-12-07 | 1 | -0/+14 |
| | |||||
* | Store GenericParams in arena | Aleksey Kladov | 2019-12-07 | 1 | -0/+10 |
| | |||||
* | DynMap | Aleksey Kladov | 2019-12-06 | 1 | -1/+4 |
| | | | | | This might, or might not help us to reduce boilerplate associated with plumbing values from analysis to the IDE layer | ||||
* | Introduce ChildFromSource | Aleksey Kladov | 2019-12-05 | 1 | -0/+1 |
| | |||||
* | Move source-related traits to a separate module | Aleksey Kladov | 2019-11-28 | 1 | -51/+3 |
| | |||||
* | Use InFile for AstId | Aleksey Kladov | 2019-11-28 | 1 | -5/+5 |
| | |||||
* | Rename Source -> InFile | Aleksey Kladov | 2019-11-28 | 1 | -13/+13 |
| | |||||
* | Rename module_id -> local_id | Aleksey Kladov | 2019-11-27 | 1 | -1/+1 |
| | |||||
* | Move Ty | Aleksey Kladov | 2019-11-27 | 1 | -1/+1 |
| | |||||
* | Decouple | Aleksey Kladov | 2019-11-27 | 1 | -0/+10 |
| | |||||
* | Introduce hir::Type | Aleksey Kladov | 2019-11-26 | 1 | -0/+10 |
| | | | | It should provide a convenient API over more low-level Ty | ||||
* | Fixme for union fields | Aleksey Kladov | 2019-11-25 | 1 | -0/+1 |
| | |||||
* | Fix hir for ast::UnionDef | Aleksey Kladov | 2019-11-25 | 1 | -18/+14 |
| | |||||
* | Merge #2396 | bors[bot] | 2019-11-24 | 1 | -6/+7 |
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2396: Switch to variant-granularity field type inference r=flodiebold a=matklad r? @flodiebold Previously, we had a `ty` query for each field. This PR switcthes to a query per struct, which returns an `ArenaMap` with `Ty`s. I don't know which approach is better. What is bugging me about the original approach is that, if we do all queries on the "leaf" defs, in practice we get a ton of queries which repeatedly reach into the parent definition to compute module, resolver, etc. This *seems* wasteful (but I don't think this is really what causes any perf problems for us). At the same time, I've been looking at Kotlin, and they seem to use the general pattern of analyzing the *parent* definition, and storing info about children into a `BindingContext`. I don't really which way is preferable. I think I want to try this approach, where query granularity generally mirrors the data granularity. The primary motivation for me here is probably just hope that we can avoid adding a ton of helpers to a `StructField`, and maybe in general avoid the need to switch to a global `StructField`, using `LocalStructFieldId` most of the time internally. For external API (ie, for `ra_ide_api`), I think we should continue with fine-grained `StructField::ty` approach, which internally fetches the table for the whole struct and indexes into it. In terms of actual memory savings, the results are as follows: ``` This PR: 142kb FieldTypesQuery (deps) 38kb FieldTypesQuery Status Quo: 208kb TypeForFieldQuery (deps) 18kb TypeForFieldQuery ``` Note how the table itself occupies more than twice as much space! I don't have an explanation for this: a plausible hypothesis is that single-field structs are very common and for them the table is a pessimisation. THere's noticiable wallclock time difference. Co-authored-by: Aleksey Kladov <[email protected]> | ||||
| * | Switch to variant-granularity field type inference | Aleksey Kladov | 2019-11-24 | 1 | -6/+7 |
| | | |||||
* | | Implement HasModule for AdtId | Aleksey Kladov | 2019-11-24 | 1 | -0/+10 |
|/ |