`ChainMap` has wrong or unintuitive type after #6042

#6042/#6044 gives me new mypy complaints on my code base.

ChainMap only ever writes to the first mapping in maps. That's my understanding. For example ChainMap({}, defaults) is a typical use-case where the user gets a dict-like and cannot mutate the defaults. That's the typical stacking property of the ChainMap, you only ever mutate the top, most recent mapping.

From my understanding:

def __init__(self):
def __init__(self, __map: MutableMapping):
def __init__(self, __map: MutableMapping, *maps: ImmutableMapping):

I don't think we can have correct hints for the maps member, and new_child of course expects a mutable mapping because iirc it is exactly the next top most thing on the stack.

Originally posted by @kaste in https://github.com/python/typeshed/issues/6042#issuecomment-1186610570

(I started this as a comment on the closed issue but closed issues don't move and I got initial supportive feedback on my comment from @hauntsaninja.)

Comienza en el punto de entrada del tipo ChainMap y revisa el contexto de las issues #6042 y #6044. Compara el constructor propuesto y los tipos de new_child con los stubs actuales; se considera terminado cuando ChainMap({}, defaults) permite mutar el primer mapping sin producir las quejas de mypy indicadas para el mapping defaults.