> I may have misunderstood how to use it, but I typed '([A])->bool' into > the web interface and expected to see vec::is_empty (amongst others) > but it just drew a blank.
Nope, just a bug (which should be fixed now) - I just rewrote the parsing code (such as it is) from an extremely simplistic initial version to a slightly-less simplistic second version, and in doing so introduced bugs (and hadn't updated all the tests… errp). I've been playing a little fast and loose with the parsing code, because I'm assuming it will be replaced very soon with the existing parser (i.e. libsyntax, whether used by way of a librustdoc or on its own). > Graydon, is all the required information already provided by libsyntax > or will Daniel indeed have to wait for a librustdoc before he can stop > scraping the HTML? My hope was to piggyback on parts of rustdoc, as my requirements are really similar (i.e., stripping a lot of information out of the AST that libsyntax produces), and I'm actually working on the librustdoc refactor (should be done very soon, just some makefile stuff), but barring that I can just use libsyntax. Or I can just incorporate it into rustdoc and share that way. > All in all, I like the idea a lot; I've never seen an api search work > like this before, and it will be useful given that (as I understand > it) recent discussion has suggested that Java/C++ -style > 'intellisense' won't work as well with Rust. Thanks for the positive feedback! It's still got a ways to go, but I've found this kind of tool very useful in haskell (for which the 'original' seach-by-type documentation tool, hoogle, was written). _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
