The current code-base outputs a lot of compiler warnings.
It'd be great to clean these all up at some stage, so that in future when we make our additions, our eyes can just narrow-in on the warnings and errors those new changes introduce (rather than wading through a tonne of existing warnings and errors).
At some stage, it may be worth enforcing the "warnings as errors" setting in the compiler on the travis-side, to ensure the committer cleans these things up before merging into master.
The current code-base outputs a lot of compiler warnings.
It'd be great to clean these all up at some stage, so that in future when we make our additions, our eyes can just narrow-in on the warnings and errors those new changes introduce (rather than wading through a tonne of existing warnings and errors).
At some stage, it may be worth enforcing the "warnings as errors" setting in the compiler on the travis-side, to ensure the committer cleans these things up before merging into master.