On Sunday, 8 September 2013 at 15:09:31 UTC, Gary Willoughby
wrote:
This is a job for the *documentation* and if documentation is
automatically generated (which it is, see '-D') then this
argument is moot.
Documentation is tool to help with cross-project learning. I have
never seen one used internally inside the same project. It simply
does not work that way, not even close in convenience to matching
source organization. Takes more time, uses different information
representation other than plain code, is not applicable in some
contexts (i.e. git log).
Built-in IDE tools are generally better for that but, as I have
already said, I am not aware of a single one that does it
conveniently enough.
Except when dealing with books, tutorials, third party
libraries, pull requests, etc...
That applies to any other possible feature that may or may not
exist in D. What I do mean though is that you shouldn't care how
third-party library is organized - for you it remains same import
statement and documentation investigation that requires to change
nothing in your code flow even if third-party library uses this
feature and you do not.
