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. On Wed, Mar 12, 2014 at 2:57 PM, Daniel Micay <danielmi...@gmail.com> wrote: > On 12/03/14 06:38 AM, Huon Wilson wrote: > > Certain aspects of them dramatically complicate the name resolution > > algorithm (as I understand it), and, anyway, they have various downsides > > for the actual code, e.g. the equivalent in Python is frowned upon: > > > http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html#importing > > > > Maybe they aren't so bad in a compiled & statically typed language? I > > don't know; either way, I personally find code without glob imports > > easier to read, because I can work out which function is being called > > very easily, whereas glob imports require more effort. > > > > > > Huon > > I think it's still pretty bad. It makes it *very* hard to read the code > because it's not clear where the names are coming from. > > > > _______________________________________________ > Rust-dev mailing list > Rust-dev@mozilla.org > https://mail.mozilla.org/listinfo/rust-dev > > -- Clark. Key ID : 0x78099922 Fingerprint: B292 493C 51AE F3AB D016 DD04 E5E3 C36F 5534 F907
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
