If I had any spare time left I'd love to work on something like this.
Kudos for giving this a try!

On 13.03.2014 08:50, Phil Dawes wrote:
FWIW I've started working on autocomplete functionality for rust.
https://github.com/phildawes/racer

I'm persuing the 'scan the source code text, incrementally parsing relevant pieces' approach. I'm also learning the language so it's a bit slow going (and will require cleanup as I become more familiar with the idioms). I've only just got libsyntax parsing individual blocks and statements and am hoping to get some type inference going over the next week or so.



On Wed, Mar 12, 2014 at 9:58 PM, Gaetan <[email protected] <mailto:[email protected]>> wrote:

    I really like anaconda with sublime. Even if the module is not
    perfectly parsable, it can display you the right info, with some
    kind of heuristic to fix type mistakes,...

    Le 12 mars 2014 22:42, "Clark Gaebel" <[email protected]
    <mailto:[email protected]>> a écrit :

        Fair enough. I didn't consider that. Note to self: rust ain't
        ocaml. :)

        On Mar 12, 2014 4:53 PM, "Daniel Micay" <[email protected]
        <mailto:[email protected]>> wrote:

            On 12/03/14 04:11 PM, Clark Gaebel wrote:
            > Honestly, I like the 98% solution of "grab metadata from
            every other
            > module in the project except the one you're editing, and
            use 'text that
            > appears before' completion (or similar heuristics) for
            things in the
            > module you're editing." It doesn't require a compiler
            that can parse
            > broken code, and is relatively minimal in work.

            How do you find the type of the value you're trying to
            complete a method
            on, like `foo.b<tab>`? You need to be able to identify the
            type and the
            in-scope traits.


        _______________________________________________
        Rust-dev mailing list
        [email protected] <mailto:[email protected]>
        https://mail.mozilla.org/listinfo/rust-dev


    _______________________________________________
    Rust-dev mailing list
    [email protected] <mailto:[email protected]>
    https://mail.mozilla.org/listinfo/rust-dev




_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to