Can we have a roadmap for static analysis in Nim? Perhaps during the [Nim Online Conference](https://forum.nim-lang.org/t/6132)?
Is drnim seen as a complement to nim compiler type checking, trying to balance speed of compilation and type checks in the compiler, with for more deep static analysis the developer would decide to delegate to drnim before integration, for instance? Static analysis can be understood with a very broad scope, some even including source pretty printers into the domain (see [previous Awesome list](https://github.com/mre/awesome-static-analysis)). Purists will say that the real goal is to find bugs before they occur when the code is executed. Where drnim will stand? Will there be a way to extend drnim with Z3 constraints/rules/nim code to add checks?
