Is this problem avoided in Typescript? I assume it still wouldn't be if the function used with map happened to take the number & types of arguments that matched

Is this problem avoided in Typescript? I assume it still wouldn't be if the function used with map happened to take the number & types of arguments that matched how map was declared, but that's rather less likely. Actually I'm now curious if Typescript would allow using parseInt as a parameter to a version of 'map' that was declared to only accept functions with a single argument - I'd guess not.