New option for variable-name rule to disallow identifiers which are also valid types in the scope

[adidahiya]

Suggested by @alexeagle here: microsoft/TypeScript#5187

Currently blocked on #680; we need the whole program's type information to be able to do this check.

[alexeagle]

Can I have an intermediate fix? For angular it would work to disallow untyped parameters in function types altogether.
I tried adding "typedef": [true, "parameter"], to our tslint config
https://github.com/angular/angular/blob/6abed8d996168f695e638c0c2d0fde1ad7ae273c/gulpfile.js#L294
but I get pages of errors, because it covers function declarations as well as function type expressions.

We like to move towards noImplicitAny in very slow steps, making each change manageable in size. So far I've written custom checks for this:
https://github.com/angular/angular/tree/6abed8d996168f695e638c0c2d0fde1ad7ae273c/tools/tslint

What do you think about more fine-grained configuration?

[JoshuaKGoldberg]

Note: per #4534, this issue will be closed in less than a month if no PR is sent to add the rule. If you really need the rule, custom rules are always an option and can be maintained outside this repo!

[JoshuaKGoldberg]

💀 It's time! 💀

TSLint is being deprecated and no longer accepting pull requests for new rules. See #4534. 😱

If you'd like to see this rule implemented, you have two choices:

• Recommended: Use typescript-eslint to lint your TypeScript code with ESLint ✅
• Legacy: Write it as a custom TSLint rule 🤷‍♂️

👋 It was a pleasure open sourcing with you!

If you believe this message was posted here in error, please comment so we can re-open the issue!

[JoshuaKGoldberg]

🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖

🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋