This is kind of the progression of #25309, and this issue's fix should be inspired by microsoft/TypeScript#27034.

Lots of users seem to be confused by misconfiguration when using popular new methods added to built-in types. A recent example is microsoft/TypeScript#40319.

The idea here come up with a static list of methods added to

This came up for fixes to svg-gradient() (less/less.js#3261). There are no automated visual regression tests, so it might be good to do so for functions that create visual assets. See: https://github.com/garris/BackstopJS

Our error messages are not consistent regarding the use of quotes, e.g. some quote the function name and contract name, others don't.

We should agree on how we want to do that and make it consistent everywhere.

@erak argues for double quotes " around all user defined names.
I tend to agree.

This is a follow-up to #4097 where we used an AtomicInteger as a poor-mans replacement for a Semaphore with tryAcquire (or maybe even drainPermits).

Should suppress --strict warnings.