Ryan Leckey

The source is not checked for errors when you merge. I'd say this is an oversight and should be corrected.

We're saying mostly the same thing. Hm. And re-reading what's going I take back what I said too. Errors _are_ checked when a source is merged in. **However** that erroring...

Didn't think someone would actually want this when I thought through it more. The dotenv lib could be used alongside this one easy enough.

I'm still planning to do this. There are many tools out there that use "generic" `.conf` files and this would satisfy that. I don't want to call the format `Dotenv`...

And I just found a good use case for supporting specifically the `.env` file. Diesel will only support loading the database URL from the environment until `#[proc_macro]` stabilizes. For now...

`config` is currently designed such that fields must be identifiers. The `.` is used to traverse nested configuration. I didn't think it was even possible for you to _set_ a...

Ah. That's a bug then. It should have produced a table at `nested.foo` with a key `bar` that is a simple Value which would have then worked fine with `config.get("nested.foo.bar")`.

@mwillsey > If I create Settings from the config file, I'll end up with Settings.bar being None, which makes sense. My question is how would I override that (or merge...

@mwillsey Hmm.. Un-define in general is a hard concept. `APP_BAR=` is understood as "undefined" not "null" (by default) as its a very common unix idiom to unset an environment variable...

I see where this is coming from. First, thanks for the contribution. I agree as well that your solution #3 is probably the best way to handle this. Very minor...