verri/cool as a dependency

[verri]

The cool library contains some useful one-header utilities.

In order to avoid having an include/dnaya/utils.h header, I propose using such a library as a git module dependency here.

Any common structure or algorithm not present in the standard library (and simple to implement) would be hosted there.

Should we need a very complex algorithm/data structure, Boost should be used instead.

[ryukinix]

We can use the vendoring dependency management concept putting in vendor directory the git submodules the third-party libraries used in the project, as we talked before. I'll take a look in that mini library, thanks @verri