Hi @joru ! From looking at that rule (and checking the source code), I don't see anything about it that is specific to typescript or that requires type information to report correctly. Therefore, I don't think we can consider it for this plugin, even though it was part of tslint... Have you checked around for a similar rule in popular JS plugins?

I don't see anything about it that is specific to typescript or that requires type information to report correctly

Technically it should use type information for cases like

declare function acceptsCb(cb: (arg1: string) => void): void;

declare function cb(...args: number[]): void;

acceptsCb(() => cb()); // no ts error
acceptsCb(cb); // will TS error

My 2c:
The motivation behind this rule is so low value -- you're saving a single FN closure which would cost nanoseconds. There's an argument for standardisation of code but even then it's a minor win, IMO.

I'm personally -1 for owning an implementation of this rule for this reason, but also I'm -1 because it's been many years since tslint was deprecated and this is the first someone has asked for the rule -- so the rule didn't see high usage within tslint. We also haven't ever had an issue asking for a similar rule (ignoring tslint) -- which further suggests that it's not something the community cares for.

Closing out as not in scope for typescript-eslint. We have a pretty limited maintenance budget and can't take on every rule that gets proposed. But if you're interested in writing this yourself, https://typescript-eslint.io/developers has docs for writing a custom rule. If you publish this as a standalone plugin and a lot of folks take it on, that would be evidence we should re-consider. 🙂 thanks for filing!