New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
processing attribute #[path] of module #1499
Conversation
Awesome! In theory this should enable completions for |
crates/ra_hir/src/nameres/tests.rs
Outdated
@@ -364,6 +364,101 @@ fn module_resolution_works_for_raw_modules() { | |||
"###); | |||
} | |||
|
|||
#[test] | |||
fn module_resolution_decl_path() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets move these and other tests that target specifically how mod
s are resoved into a new nameres/tests/mods.rs
submodule?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, of course
bors r+ Thanks! |
Build succeeded |
On
to
|
I can confirm that RA can now display completions for |
@marcogroppo new issue? |
I'll submit a PR! |
1514: Better completions for floating point primitive types r=flodiebold a=marcogroppo After #1499 completions for (some of) the inherent methods of `f32` and `f64` are now working. Unfortunately during method resolution we were only looking for the `f32` and `f64` language items defined in `libcore` and we were ignoring the methods defined in `libstd`. This PR fixes this issue. Co-authored-by: Marco Groppo <marco.groppo@gmail.com>
support two cases
foo.rs
#1211