3 ms·
Both of those are in my use case outright impossible given the dynamicity/duck-typing-ness level of the code I operate with (Python, Ruby), where the editor has
by lloeki 14y ago
Both of those are in my use case outright impossible given the dynamicity/duck-typing-ness level of the code I operate with (Python, Ruby), where the editor has no freezing chance in hell of guessing what might come out of this variable (unless maybe if the editor is the runtime and everything is live... smalltalk!)
This is why for me "free-form refactoring without relying on fixed-form refactoring routines and plugins (i.e not just a glorified search and replace)."[0] (which is a comment by myself made 6 days ago, that actually makes the same point as TFA) is extremely important.
As for discovery through autocompletion, I find my need for it has been greatly reduced these last years, with a growing number of APIs that "make sense", hence discovery happens in your head, not on the screen. If the API is obtuse to the point it doesn't fit in my head, then I usually need the doc so I'll have it open nearby anyway.
[0]: https://news.ycombinator.com/item?id=5414050 https://news.ycombinator.com/item?id=5414050
- jeremyjh 14y agoYou might be surprised at this. I've used the Python tools for Visual Studio and it has some type awareness; I think perhaps what it is doing is capturing the type of a variable at runtime when you execute your program and using that while you are coding. In either case, intellisense works quite well (though not when you first introduce a new variable). I've also used RubyMine and it has some pretty nice inspection features; it will highlight issues such as parameter agreement, unused locals and many other things. It is not like a static language but still quite helpful (and never unhelpfully wrong). I use the VSVim plugin in Visual Studio and IDEAVim in IDEA/RubyMine and they work great (ideavim is kind of lame as it has no real keymap support, but its better than nothing).