Havoc Pennington

Might be mixing some different things into this issue (representing dots in keys in the Config data structure, vs. representing values-stored-at-parent-nodes). The `__value__` idea would be a somewhat leaky abstraction......

I would quote the string like "google.com" ... doesn't seem like a workaround to me?

root() gets you a `ConfigObject` so the key set will be the JSON-style string keys, not path expressions. Since `"google.com"` was quoted it will be one key so the keySet...

`Config` is keyed by path expressions; `ConfigObject` is keyed by unparsed strings. Conceptually it is a type error to pass a path expression where a string is expected or vice...

https://github.com/lightbend/config/issues/365 seems to be the best current discussion and the issue is still open. I don't have plans to work on this myself (this library has little or no active...

I don't disagree that it's worth looking at. To be clear, _nothing_ is getting attention right now, so this isn't thrown aside in particular, it's just part of the general...

Let me back up to the big picture for a minute. ## Background on the library design The intuitive issue is what does it mean for an app to rely...

All that past rationale aside, I should also have asked - what immediate specific thing are you doing where preserving order would be useful? What problem are you trying to...

If the answer is as simple as insertion order, can we make my proposed associativity test case pass with that answer? > The order of loading values is already well...

> Are these operations not atomic and completely separate from each other? They are ... but only if `withFallback` is associative. The test you wrote is the right one but...