Now that Nimble offers nimscript I actually think it should be the other way around. `config.nims` should be deprecated. This may sound crazy, but I don't see why we should have two tools that offer the same functionality. The nim.cfg format works incredibly well for configuring the compiler and I am yet to run into a use case where I need to use full-blown Nim when I'm configuring Nim...
- should we deprecate nim.cfg in favor of config.nims format? timothee
- Re: should we deprecate nim.cfg in favor of config.nim... moigagoo
- Re: should we deprecate nim.cfg in favor of config... kaushalmodi
- Re: should we deprecate nim.cfg in favor of co... dom96
- Re: should we deprecate nim.cfg in favor o... juancarlospaco
- Re: should we deprecate nim.cfg in fa... gemath
- Re: should we deprecate nim.cfg i... andrea
- Re: should we deprecate nim.c... gemath
- Re: should we deprecate nim.c... andrea
- Re: should we deprecate nim.c... arnetheduck
- Re: should we deprecate nim.c... andrea
- Re: should we deprecate nim.c... juancarlospaco
- Re: should we deprecate nim.c... Araq
- Re: should we deprecate nim.c... timothee
