> Wow, this is looking pretty great! I'm definitely looking forward to the > search functionality; it'll save me loads of time. Will it just search > function/module names, or also descriptions?
We'll need to see what's feasible since this needs to be a plain js solution, but I guess we can do at least names and short descriptions. I guess parsing through the entire descriptions will be rather slow and will yield tons of false positives. In any case this is not my specialty so if anyone has a clue or wants to help ping me on #rustdoc-wg > What about having the > documentation link the the appropriate source files on Github (or > embedding them within the page)? If it's tied into the Github API, could > it also show open issues relating to certain modules, or perhaps > TODOS/XXX within them? It isn't tied to the GH API no, though I suppose if we see #\d+ in comments we could infer that they are issue numbers and link to that. Regarding the source, there is a "[src]" link (icon pending) on every page that brings you to the definition in the libstd source. Cheers -- Jordi Boggiano @seldaek - http://nelm.io/jordi _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
