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.

Attachment: signature.asc
Description: OpenPGP digital signature

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

Reply via email to