Wez Furlong da7da888cd config: generate errors for things like --config tarm=foo ... Invalid option names, or values that evaluate as nil (such as the `foo` above: that's treated as a global variable reference, but `foo` isn't a defined global and evaluates as `nil`) will now cause the program startup to error out with an actionable error message. Previously, the invalid config name would generate a warning, and the invalid value would silently have no effect as it has the same effect as omitting the named value and leaving it as its default value. I think these cases should both immediately error out and stop further processing, so that's what we're doing. This commit also adds support for adding: ``` #[dynamic(deprecated = "use newer option instead")] pub some_config_value: bool, ``` but not options currently use this.		2022-05-21 13:10:30 -07:00
..
src	config: generate errors for things like --config tarm=foo	2022-05-21 13:10:30 -07:00
build.rs	ci: use consistent git core.abbrev setting for TAGNAME	2021-12-05 19:21:06 -07:00
Cargo.toml	deps: prune some unused deps	2022-05-19 06:48:09 -07:00