Pretty much all Nim projects use a consistent naming style, so this is not a problem in practice. > Nim should take advantage of the 2.0 release to do a compat

Pretty much all Nim projects use a consistent naming style, so this is not a problem in practice. > Nim should take advantage of the 2.0 release to do a compatibility break in this area, maybe with a compiler flag to enable the legacy behavior. No thanks, I don't want inconsistent naming conventions in my code.