Interfaces in Go make it hard to navigate code

Re:Interfaces in Go make it hard to navigate code by tomp on Monday May 27, 2013 @05:00AM (#5773973)

I think this could mostly be solved by automatic documentation generation tools and/or IDEs. Just like Java IDEs and JavaDoc index the world and show relations (i.e. classes that implement an interface), so could (and probably will) Go tools do so.

[ Parent | on HN ]

Re:Interfaces in Go make it hard to navigate code by pjmlp on Monday May 27, 2013 @05:07AM (#5773985)

Well at least it is not only Java requiring IDEs then. :)

[ Parent | on HN ]

Re:Interfaces in Go make it hard to navigate code by Mr_T_ on Monday May 27, 2013 @07:33AM (#5774255)

People are programming in completely dynamic, duck typed languages and say that these languages are best without IDE.

[ Parent | on HN ]

Re:Interfaces in Go make it hard to navigate code by pjmlp on Monday May 27, 2013 @12:28PM (#5775214)

Funny you say that, because the first IDEs were actually invented for dynamic languages (Smalltalk & Lisp).

[ Parent | on HN ]