code: public static Config parseMap(Map<String, ? extends Object> values,
              String originDescription) {
          return ConfigImpl.fromPathMap(values, originDescription).toConfig();
      }
docs: Creates a {@code Config} based on a {@link java.util.Map} from paths to
  plain Java values. Similar to
  {@link ConfigValueFactory#fromMap(Map,String)}, except the keys in the
  map are path expressions, rather than keys; and correspondingly it
  returns a {@code Config} instead of a {@code ConfigObject}. This is more
  convenient if you are writing literal maps in code, and less convenient
  if you are getting your maps from some data source such as a parser.
  
  <p>
  An exception will be thrown (and it is a bug in the caller of the method)
  if a path is both an object and a value, for example if you had both
  "a=foo" and "a.b=bar", then "a" is both the string "foo" and the parent
  object of "b". The caller of this method should ensure that doesn't
  happen.
  
  @param values map from paths to plain Java objects
  @param originDescription
  description of what this map represents, like a filename, or
  "default settings" (origin description is used in error
  messages)
  @return the map converted to a {@code Config}