@ggibson, you captured perfectly my thoughts with your "ambiguous or confusing compiler errors" comment. It's not that the error messages are bad but that sometimes they require a lot of nim knowledge to understand them. This makes them not that helpful sometimes unless you really know what you are doing (which unfortunately is not my case yet).
As an example, the errors that you get when you do "include std/prelude" instead of "import std/prelude" make sense once you know what the problem is but they did not help me detect the problem until @ynfle pointed it out to me.
