There should be a rule to disallow untyped function parameters but allow return type inference

[minenwerfer]

Feature

A no-untyped-parameters rule which will output an error if the signature of a function has untyped parameters but will allow inferring this function return type. It is somewhat how TypeScript's noImplicityAny currently works. Existing function signature rules will require parameters to be annotated but also the return type.

The following should give an error (parameter a isn't typed):

def fn(a): ...

The following shouldn't, and the return type should be inferred as int:

def fn(a: int): return a

[erictraut]

I think this is a duplicate of #10149.

[AlexWaygood]

I think this is a duplicate of #10149.

yes