vector-of-bool
vector-of-bool
You've expressed distaste for `install()` rules, but would you be opposed to their addition as an optional feature? I'd be interested in having/adding such a thing myself.
Is there an intention to add library concepts in place of the current named requirements? There's admittedly some challenges in doing so, but I enjoy the benefits of clearer error...
This PR is part suggestion, part implementation. If you can think of an easier to do what I'm trying to do, I'm all ears. I have an application that has...
**Describe the scenario and circumstances that should be addressed** `dds`'s current handling of repositories is poor from a security perspective. Currently, `dds` will connect to repositories via HTTPS happily, but...
**Describe the scenario and circumstances that should be addressed** - If all of the source files in a compiled library are identical to their previous build results, they do not...
**Describe the scenario and circumstances that should be addressed** Semantic versioning offers some guarantees about compatibility between version numbers. It would be excellent if `dds` could automatically test these guarantees....
**Describe the scenario and circumstances that should be addressed** `dds` doesn't cache generated binaries, instead relying on external tools such as CCache. `dds` has special understanding of the build process...
**Existing Behavior and Potential Problems** Currently, `dds` considers every compilation flag to be relevant to incremental compilation. This isn't true for some flags, such as GCC/Clangs `-fdiagnostics-color` or MSVC's `/nologo`....
**Describe the bug** When cached compiler output is printed, or when printing errors from a failed compile command, the output of MSVC is not pruned of deps information nor the...
**Describe the scenario and circumstances that should be addressed** Every `dds` repository should have a **globally** unique name. `dds` stores each package listing alongside the repository that contains it, so...