On 12/03/14 03:12 PM, Clark Gaebel wrote:
> That implies we need better editors. Things I need for exploring large
> codebases:
> 
> 1. Go to definition
> 2. What's the type of this variable/function?
> 
> With these two things, it should be relatively easy to read code with or
> without glob imports.

Rust is explicitly designed to work well in any editor. That's one of
the reasons for caring so much about keeping the grammar simple. It's a
pragmatic language ignoring arguments about a sufficiently smart
compiler or editor.

There is no accurate jump-to-definition, type retrieval, docstring
retrieval or semantic completion for Rust. The compiler was not built
with support for this kind of tooling in mind, and I seriously doubt
that anything but inaccurate hacks will exist for a *long* time. Even if
it did exist, there would be many editing Rust code without it. Not
everyone is going to install a librustc-based emacs/vim plugin,
completion daemon or whatever is required.

Attachment: signature.asc
Description: OpenPGP digital signature

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

Reply via email to