Disallow assignment of `Any` to known/explicit types and/or Introduce `Unknown` type

Feature

I'd like an option that prevents assigned of the Any type to something with a known type, in particular places where I've specified the type.

Returns:

def return_type_a() -> TypeA:
   untyped = {}
   return untype  # Disallow

Assignement:

store : Dict[StoreRef,StoreItem = {}

def create() -> Dict:
  return {}

store = create()  # Disallow

Pitch

It'd be nice to have a stricter boundary between typed and untyped code. The samples I show above are frequent sources of error for me and they quietly slip by the type checking.

While migrated code there are still a lot of Any's in the code, and in some domains they'll never go away (when dealing with genuinely generic data structures, also now since some recrusive types, like JSON, need to use Any).

Related

An explicit Unknown type, in contrast to Any, would also help a lot. TypeScript has an unknown and it is helpful for dealing with generic data and not accidentally using it as the wrong type.

If an Unknown was available the above could also be achieved by turning on the "disallow any" flags and using Unknown in places where generic data is needed.

Commencez par lire la gestion de Any par mypy et ses flags disallow-any existants, en utilisant les exemples de retour et d'affectation comme cas de comportement. Clarifiez si le travail couvre des vérifications d'affectation plus strictes, un type Unknown ou les deux ; le travail est terminé lorsque le comportement sélectionné est spécifié et appliqué sans casser l'utilisation légitime de données génériques.