Congrats on Nim v0.12!!
Now please, please, could someone release (or tag, I'm not sure if there's a difference) v0.12 in the nimsuggest repo? This is so that people who get Nim via OS packages don't get orphaned as nim devel, and hence nimsuggest, evolves further.
Well... Not sure if thats just me but:
> nimble install nimsuggest
....
Installing compiler-0.11.3
compiler-0.11.3 already exists. Overwrite? [y/N]
Nimble obtains a package from the (GitHub) repo for that package. Without a tag in the repo, nimble can only retrieve the package version at #HEAD. This means that, as soon as the bleeding edge of nimsuggest (corresponding to nim devel?) loses compatibility with Nim v0.12, those who install Nim v0.12 via OS package are left in the cold.
This has already happened for v0.11.2 - I hope it doesn't happen here as well.
Unfortunately we forgot to change the version in compiler.nimble before tagging. So now nimsuggest cannot simply depend on compiler 0.12.0, Araq updated the version in a recent commit so I can bump the version on nimsuggest to 0.12.0 and make it depend on that commit of the compiler. I tried to do this but ran into a Nimble bug... (:(), seems support for depending on a commit hash has been broken, I can fix it but you guys will then need the HEAD of Nimble to install nimsuggest which isn't ideal (I can of course also release a new Nimble version)
An alternative is to re-tag the 0.12.0 version of Nim. Might be far too late for that now.
Sorry about this!