> I'm hopeful that type inference combined with class syntax and an (eventual) > traits system will get us "there", so that you can use structural type tests > for enforcement and that the IDE can get the benefit of hints through > inference.
Yes. Can’t wait. > That said, I think the "I want to refactor automatically" use-case is sort of > over-played. Indeed. The type-system related features I use most often in Eclipse are: - *Safely* renaming a method or function. I do this frequently to keep the vocabulary used in methods etc. fresh. All JS IDEs that I have tried are not much fun in this regard. - Jump to the definition of a method/function. - Find all invocations of a method/function. Often, I just change the name of a method (e.g. by appending an "x") and go through all the errors that that produces. Anything else (extracting or inlining a method, etc.) is nice to have, but not as crucial. I love that JS’s more dynamic nature often lets me keep inheritance hierarchies flatter. -- Dr. Axel Rauschmayer [email protected] twitter.com/rauschma home: rauschma.de blog: 2ality.com _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
