everything that can be done with nim.cfg can be done with config.nims (after a number of issues were fixed in past few months), and config.nims is also much more featureful, so the question is:
should we deprecate nim.cfg in favor of config.nims format? ## arguments for deprecating nim.cfg * major argument: 1 config system to maintain, learn about, not 2 * major argument: nim.cfg has a number of obvious limitations, eg: [nim.cfg: how to have conditional flags to depend on compiler version? - Nim forum]([https://forum.nim-lang.org/t/4081#25755](https://forum.nim-lang.org/t/4081#25755)) > I think it's impossible to do that in nim.cfg. Sorry. and many others limitations * minor: nimscript is essentially nim syntax unlike cfg format (eg: @if ... @end syntax) so makes it easier to switch back and forth between nim and nims * minor: fixes [https://github.com/nim-lang/Nim/issues/9405](https://github.com/nim-lang/Nim/issues/9405) ## arguments for not deprecating nim.cfg * need to port existing nim.cfg to config.nims This should be largely automatable though * @araq said here: [https://github.com/nim-lang/Nim/issues/9405#issuecomment-430610040](https://github.com/nim-lang/Nim/issues/9405#issuecomment-430610040) Ok. Deprecation of the old config system is tough as long as the new config system is so slow. :-( but I'm not sure what he means by slow here; any pointer would be helpful; @araq? * links: [https://github.com/nim-lang/Nim/issues/9405#issuecomment-431866723](https://github.com/nim-lang/Nim/issues/9405#issuecomment-431866723)
