Potential future steps for the project
Hi,
I have known about the project for quite some time now, but was never able to kickstart the changes I wanted, yesterday I took a first step, I plan to slowly continue in the coming months, so I wanted to start a conversation here.
The small step I took is to create a VSCode extension (https://marketplace.visualstudio.com/items?itemName=AlperenKeles.roogle) hosted in my fork (https://github.com/alpaylan/roogle/tree/main/vscode-roogle). I have a few more thing in mind:
- Allow multi-hop search
- Allow type variables in the search (I think if I currently type
A, it searches for allfn<A: Trait>(_: A)functions, I would like to be able to sayA -> AwhereAis just any type. - Allow for partial function name search, so
fn Xdoesn't have to match justX, but also other functions based on edit distance. - Work closer to what
rust-analyzeris, in the sense that whenever the user starts working on a Rust project, we spawn a roogle server in the background, indexing/updating silently, letting user set a number of crates they are interested in searching instead of 1 and defaulting to all available in the codebase, perhaps filling type holes in the code automatically with a code action.
Through these changes, the project would change quite a bit, so I wanted to get your approval before using the name roogle, I can also just switch to another name as a new community fork, or could take part in the maintenance of the project if that's the way you would desire it.
Note: Most of the changes currently in the fork are AI generated with my guidance, that was for the purposes of creating a PoC. I'm not trying to take credit with AI generated code that hasn't been reviewed, wanted to clear this up as I see OSS projects suffering from such situations, you can view my other repositories for the quality of the work I do.