aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_def/src/item_tree.rs
Commit message (Collapse)AuthorAgeFilesLines
* internal: intern `TypeBound`sJonas Schievink2021-05-241-2/+2
| | | | | Doesn't save much memory (~2 mb), but interning things is generally a good pattern to follow
* internal: document ItemTree designJonas Schievink2021-05-231-2/+32
|
* Add an ItemTree pretty-printerJonas Schievink2021-05-211-0/+11
|
* Remove `StructDefKind`Jonas Schievink2021-05-211-11/+0
|
* Don't lower extern block in the ItemTreeJonas Schievink2021-05-211-0/+13
|
* Precompute macro fragment kindJonas Schievink2021-05-091-1/+2
|
* Don't store call-site text offsets in hygiene infoJonas Schievink2021-05-061-1/+1
|
* Remove `ItemTree::all_inner_items`Jonas Schievink2021-04-211-7/+0
|
* hir_def: various cleanupscynecx2021-04-181-4/+4
|
* hir_def: ignore ast::Type in file_item_tree querycynecx2021-04-171-0/+5
|
* Support macros in pattern positionJonas Schievink2021-04-111-0/+5
|
* Intern `GenericParams`Jonas Schievink2021-04-051-54/+7
| | | | | Also share the same instance between `ItemTree` and `generic_params` query.
* Check if bitflags deps pulls its weightAleksey Kladov2021-04-041-14/+15
| | | | | | | | Bitflags is generally a good dependency -- it's lightweight, well maintained and embraced by the ecosystem. I wonder, however, do we really need it? Doesn't feel like it adds much to be honest.
* Use bitflags to compress function propertiesJonas Schievink2021-04-031-14/+17
| | | | Very minor savings, only 1 MB or so
* Intern `ModPath` in `Import`Jonas Schievink2021-04-031-1/+1
| | | | Minor savings only
* Intern Attr, MacroCall and Path componentsJonas Schievink2021-04-011-1/+1
|
* Global TypeRef/TraitRef interningJonas Schievink2021-04-011-83/+9
|
* Rename target_ty to self_tyLukas Wirth2021-03-291-1/+1
|
* Lower traits to TraitRef instead of TypeRefLukas Wirth2021-03-291-2/+39
|
* Fix recursive macro statement expansionEdwin Cheng2021-03-251-9/+0
|
* Merge #8082bors[bot]2021-03-181-0/+4
|\ | | | | | | | | | | | | | | | | | | | | | | 8082: Proper handle inner recursive macro rules cases r=edwin0cheng a=edwin0cheng Fixes #7645 cc @jonas-schievink bors r+ Co-authored-by: Edwin Cheng <[email protected]>
| * Handle inner recursive macro rules casesEdwin Cheng2021-03-181-0/+4
| |
* | Rename `item_tree` query to `file_item_tree`Jonas Schievink2021-03-181-2/+2
| |
* | Make `ItemTreeId` its own typeJonas Schievink2021-03-181-1/+41
| |
* | Apply `#[cfg]`s when computing function signaturesJonas Schievink2021-03-171-0/+6
| |
* | ItemTree: lower attributes on fn parametersJonas Schievink2021-03-171-4/+14
|/
*-. Merge #7900 #8000bors[bot]2021-03-161-4/+15
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7900: show function params in completion detail r=matklad a=JoshMcguigan This resolves #7842 by updating the detail for function completions from `-> T` to `fn(T, U) -> V`. I added an expicit unit test for this, `ide_completion::render::fn_detail_includes_args_and_return_type`, which passes. Lots of other unit tests fail (~60 of them) due to this change, although I believe the failures are purely cosmetic (they were testing the exact format of this output). I'm happy to go update those tests, but before I do that I'd like to make sure this is in fact the format we want for the detail? edit - I realized `UPDATE_EXPECT=1 cargo test` automatically updates `expect!` tests. Big :+1: to whoever worked on that! So I'll go ahead and update all these tests soon. But I still would like to confirm `fn(T, U) -> V` is the desired content in the `detail` field. 8000: Use hir formatter for hover text r=matklad a=oxalica Fix #2765 , (should) fix #4665 Co-authored-by: Josh Mcguigan <[email protected]> Co-authored-by: oxalica <[email protected]>
| | * Use hir formatter moreoxalica2021-03-151-1/+3
| | |
| | * Introduce FunctionQualifier for hir::FunctionDataoxalica2021-03-151-3/+12
| | |
* | | Fix macro expansion for statements w/o semicolonEdwin Cheng2021-03-161-0/+5
| |/ |/|
* | Remove `ItemTree::source`Jonas Schievink2021-03-121-12/+0
|/ | | | `HasSource` should be used instead
* Use upstream cov-markLaurențiu Nicola2021-03-081-1/+0
|
* Make `ModPath`'s representation privateJonas Schievink2021-02-041-5/+3
|
* Intern `TypeRef`s in the containing `ItemTree`Jonas Schievink2021-02-041-8/+46
|
* Use block_def_map in body loweringJonas Schievink2021-02-031-1/+5
|
* Revert "Use block_def_map in body lowering"Jonas Schievink2021-02-021-5/+1
|
* Use block_def_map in body loweringJonas Schievink2021-02-011-1/+5
|
* ItemTree: Treat items in `MacroStmts` as top-levelJonas Schievink2021-01-281-4/+6
|
* Derive Default on ItemTreeLaurențiu Nicola2021-01-251-11/+2
|
* Include `countme` crate to count important data structures.Aleksey Kladov2021-01-211-1/+9
|
* Add name resolution query for block expressionsJonas Schievink2021-01-211-0/+7
|
* Create a mapping from blocks to inner itemsJonas Schievink2021-01-201-17/+11
|
* Remove `item_tree::Expr`Jonas Schievink2021-01-181-9/+1
| | | | It's empty and unused
* Use ‘index’ terminology for arena consistentlyAramis Razzaghipour2021-01-171-1/+1
|
* prepare to publish el libro de arenaAleksey Kladov2021-01-141-1/+1
|
* Add ConstParams to the HIRLukas Wirth2021-01-011-2/+7
|
* Don't look at attributes when lowering to ItemTreeJonas Schievink2020-12-181-4/+1
| | | | Resolves 2 `cfg_attr` FIXMEs
* Refactor attributes API to allow handling cfg_attrJonas Schievink2020-12-181-7/+12
|
* Avoid querying attributes in item tree loweringJonas Schievink2020-12-161-8/+0
| | | | | | | | ItemTree is per-file, so there is no unique crate associated with it. This means that it cannot know the active CfgOptions and thus couldn't handle `cfg_attr`. Prepare it for `cfg_attr`s by avoiding accessing attributes.
* Basic support for decl macros 2.0Jonas Schievink2020-12-151-2/+18
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-04 22:33:17 +0100