On Thursday, 23 June 2016 at 13:31:37 UTC, Guido wrote:
But I have to say that more detailed descriptions of commands
is not what I had in mind. What are the best coding practices
and why?
I obviously haven't started using dub yet, so I won't be able
to judge whether a code example is merely adequate or very
robust. For example, why subpackages? It's in there for a
reason; what situations call for subpackages? Why use
-ddoxFilterArgs? When & how to static link? What dub-based
project does a good job building for multiple platforms?
From what's been discussed, I should always specify version
number. Is there some best practice for flagging when a change
to dependencies breaks your code? I would create a build type
that lists the latest version of each dependency & run
unittests. Is there a better way that someone is using in the
field?
It wouldn't be much of a handbook if it didn't cover usage. Of
course I will give examples, with tips based on how I use it and
any I can gather from other users. Once I make it available for
feedback, feel free to suggest anything you feel is missing.
