aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_hir/src/nameres.rs
Commit message (Collapse)AuthorAgeFilesLines
* Fix clippy::iter_cloned_collectAlan Du2019-06-041-4/+2
|
* Fix clippy::option_map_or_noneAlan Du2019-06-041-1/+1
|
* Fix clippy::or_fun_callAlan Du2019-06-041-6/+11
|
* Fix clippy::identity_conversionAlan Du2019-06-041-1/+1
|
* add AstDatabaseAleksey Kladov2019-06-021-5/+8
|
* Improve goto definition for MBEEdwin Cheng2019-06-011-2/+16
|
* add built-in types to scopesAleksey Kladov2019-05-301-4/+15
|
* add list of builtin typesAleksey Kladov2019-05-301-1/+1
|
* add cacellation checks to expensive queriesAleksey Kladov2019-05-291-0/+1
|
* Use ItemOrMacro in item resolutionEdwin Cheng2019-05-261-34/+81
|
* simplifyAleksey Kladov2019-05-121-2/+2
|
* Added macro resolution and expansionLenard Pratt2019-04-221-0/+6
|
* Add mbe expand limit and poision macro setEdwin Cheng2019-04-221-1/+15
|
* Initial support for lang items.Marco Groppo2019-04-191-0/+4
|
* use either for usesAleksey Kladov2019-04-101-1/+1
|
* Merge #1068bors[bot]2019-04-031-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | 1068: profiling crate first draft r=matklad a=pasa I've made this first draft for #961 Could you look at it? Is this something what you are looking for? It has lack of tests. I can't figure out how to test stderr output in rust right now. Do you have some clues? Additionally I'm thinking about to implement procedural macros to annotate methods with this profiler. Will it be helpful? Co-authored-by: Sergey Parilin <[email protected]>
| * Merge remote-tracking branch 'upstream/master' into issue961_profilingSergey Parilin2019-04-021-48/+67
| |\
| * | PR issuse resolvedSergey Parilin2019-04-021-2/+2
| | |
* | | always produce source for importAleksey Kladov2019-04-021-2/+5
| |/ |/|
* | add typed idsAleksey Kladov2019-03-261-10/+10
| |
* | remove some dead codeAleksey Kladov2019-03-261-17/+1
| |
* | simplifyAleksey Kladov2019-03-261-4/+2
| |
* | move source_id to a separate fileAleksey Kladov2019-03-261-1/+2
| |
* | store macro def inside macro idAleksey Kladov2019-03-261-9/+2
| | | | | | | | | | | | | | | | This solves the problem of "macro expansion can't call into name resolution, because name resolution calls back into macro expansion" Because we store macro def as a part of call id, macro expansion just knows the def!
* | Basics for trait method resolutionFlorian Diebold2019-03-251-1/+7
| |
* | fixesAleksey Kladov2019-03-251-1/+1
| |
* | check impls as wellAleksey Kladov2019-03-251-1/+1
| |
* | cleanupAleksey Kladov2019-03-251-25/+41
| |
* | switch modules to new diagnosticsAleksey Kladov2019-03-251-22/+43
|/
* rename persistent hir database -> def databaseAleksey Kladov2019-03-231-9/+6
|
* replace todo with fixmeAleksey Kladov2019-03-231-1/+1
|
* docsAleksey Kladov2019-03-171-9/+15
|
* remove old macro supportAleksey Kladov2019-03-171-3/+26
|
* rename ModuleId -> CrateModuleIdAleksey Kladov2019-03-171-15/+15
|
* log timeAleksey Kladov2019-03-171-0/+2
|
* Reorganize name resolutionAleksey Kladov2019-03-171-100/+362
|
* remove ItemMapAleksey Kladov2019-03-171-535/+4
|
* move tests over to crate-def-mapAleksey Kladov2019-03-171-4/+1
|
* Replace module_tree with CrateDefMapAleksey Kladov2019-03-171-11/+12
|
* add skeleton for macro-aware name resolutionsAleksey Kladov2019-03-171-0/+1
|
* align lower module query namesAleksey Kladov2019-03-021-1/+1
|
* Fix resolution of associated method calls across cratesFlorian Diebold2019-02-231-1/+5
| | | | | | I think it'll be better to make the path resolution the number of unresolved segments, not the first unresolved index; then this error could simply not have happened. But I'll do that separately.
* Make nameres::ResolvePathResult private and refactorVille Penttinen2019-02-211-7/+7
|
* Remove Const inference for now, refactor PathResultVille Penttinen2019-02-211-15/+8
|
* Implement basic support for Associated Methods and ConstantsVille Penttinen2019-02-211-16/+62
| | | | | | | This is done in `infer_path_expr`. When `Resolver::resolve_path` returns `PartiallyResolved`, we use the returned `Resolution` together with the given `segment_index` to check if we can find something matching the segment at segment_index in the impls for that particular type.
* Handle tuple structs / enum variants properly in type inferenceFlorian Diebold2019-02-171-2/+2
|
* Complete names from preludeFlorian Diebold2019-02-131-1/+1
|
* Handle extern crates better, so they work correctly in 2015 editionFlorian Diebold2019-02-131-8/+17
| | | | (see the removed comment.)
* Resolve 2015 style importsFlorian Diebold2019-02-131-7/+61
|
* Import the preludeFlorian Diebold2019-02-131-4/+46
|