I agree with the typing arguments. A config parser can only parse the values to a degree, to primitive types basically. The application can parse them fully. So

I agree with the typing arguments. A config parser can only parse the values to a degree, to primitive types basically. The application can parse them fully. So the question is to what extent the parser helps the application vs to what extent it introduces subtle problems. As a config file user I would prefer not to have to care so much, but also not to have to work around weird corner cases. YAML's no-problem is a perfect example. This would not exist if the parser did not try to be helpful. I am in the author's camp.