Skip to content
This repository has been archived by the owner on Nov 14, 2021. It is now read-only.

Home

Jump to bottom
dobkeratops edited this page Sep 23, 2013 · 28 revisions

overview-of-codebase

ideas-for-rust-ide

brainstorm

cross-crate-map - describes the RFX files node dumps used to link between crates

Commandline use

rustfind crate_root.rs [-x where_to_find_library_source/rfx] // emit html (&rfx) .. eg generate these in the root of rust source tree, then generate in current project dir

rustfind -r crate_root.rs
// just create a .rfx ast/jump def file //(need for showing defs between crates)

you'd have to copy the .css into all dirs , someone told me to decouple style from content, whats the neatest way do deal with that..

IDE component ??

could this be extended to make a component for integrating rust support to an ide..

'interactive mode' was intended to be a step in this direction,eg something that can be fired up by an editor plugin currently this responds to queries of :: with the location of the definition. If you dont specify 'sourcefile', it uses the last sourcefile mentioned. TODO if you dont specify column-number, lookup all useful defs' on that line?

TODO

  • modify its protocol to match an existing tool for a different language (eg emacs clang autocomplete?) look at vi youcompleteme?

  • query type information of symbols

  • find definition by name, and return all possible definitons with their containing scope

  • query methods/member variables suppported by a type

  • autocomplete, like the clang plugins .. possibly supporting the same protocol as the emacs clang plugin?

RFX Files - AST dump / cross-crate metadata

(see "crosscratemap.rs" the '.rfx' is related to the CrossCrateMaps' in the source)

Allow crates to reference eachothers definitions, 'rustfind' spits out a .rfx file holding ast node &definition information; when compiling html for a given crate, it reads in any availalbe .rfx files for the library crates it references, and uses those to figure out correct jump-to-def info This is seemingly needed because the crate metadata doesnt (to my knowledge) include source information.. just whats needed to figure out correct function calls and generic function expansions

its possible the rust toolchain has this data somewhere for debugging? but at the time it wasn't conviniently accessible to me

Clone this wiki locally