This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Are you interested in upstreaming this to rustdoc? #12
Comments
I think that the upstreaming is feasible if not straightforward. We need to host another dedicated API server or upgrade the existing instance. Latterly, I'll go bankrupt though. However, I and 2 |
Maybe worth opening a thread on Zulip on this? |
Docs.rs has access to (more or less) all crates, it'd be interesting to try and make roogle work with something like rustdoc's json output to allow it to operate over all documentation. |
Luckily enough, the index is the output of rustdoc's json backend now. I think the most realistic approach here is that, add index and WASM of roogle to the resulting files of |
Yah, that definitely sounds good to me. In fact, it's much easier and could still provide cross-crate searches with some sort of "add crate" functionality (that is, you select crates to add to your search pool) and the site sends across the extra indices to be searched. |
I need some elaboration on the "add crate" feature. Is this something like users requests a crate to be added to the search index? By the way, roogle now partially achieves the cross-crate search so please check that out (cf. b0ff61b). |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I haven't looked in detail how roogle currently works, but I would love for it to be the default search rustdoc uses for the standard library and docs.rs :) would you be interested in working on that if I help out with the rusrdoc-specific parts?
The text was updated successfully, but these errors were encountered: