aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_def/src/item_tree.rs
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* Move to upstream `macro_rules!` modelJonas Schievink2020-12-151-4/+15
|
* Expand statements for mbe in loweringEdwin Cheng2020-12-151-0/+3
|
* Ignore lifetime params in substitutionsLukas Wirth2020-12-131-1/+4
|
* Add Lifetimes to the HIRLukas Wirth2020-12-111-1/+1
|
* Remove item tree testsJonas Schievink2020-12-101-2/+0
| | | | | They were useful during initial development of the item tree, but now just cause churn
* Ignore extern items in incorrect-case checkJonas Schievink2020-12-101-0/+5
|
* Add a (hint) diagnostic for unconfigured itemsJonas Schievink2020-10-201-0/+18
|
* Differentiate method/tymethod by determining 'defaultness'Zac Pullar-Strecker2020-10-081-0/+1
| | | | | | | | | Currently a method only has defaultness if it is a provided trait method, but this will change when specialisation is available and may need to become a concept known to hir. I opted to go for a 'fewest changes' approach given specialisation is still under development.
* Give `ExternCrate` a `Name`, not a `ModPath`Jonas Schievink2020-09-171-1/+1
|
* Merge #6016bors[bot]2020-09-171-1/+5
|\ | | | | | | | | | | | | | | | | | | 6016: Emit diagnostics for unresolved imports and extern crates r=jonas-schievink a=jonas-schievink AFAIK, we don't have any major bugs in name resolution that would cause a lot of false positives here (except procedural attribute macro support and some rare issues around `#[path]` on module files), so these are *not* marked as experimental diagnostics right now. I noticed that diagnostics in a file sometimes don't get displayed after opening, but require some edit to be performed. This seems like a preexisting issue though. Co-authored-by: Jonas Schievink <[email protected]>
| * Store `Import` indices for later reconstructionJonas Schievink2020-09-161-1/+5
| |
* | Update chalk to 0.27 and adapt to chalk changes.Charles Lew2020-09-151-0/+1
|/
* Rename ra_hir_def -> hir_defAleksey Kladov2020-08-131-0/+754