Some Intrinsic types have overloaded methods: 👀 `roString`

[markwpearce]

There may be others, but ifStringOps has a few:

Instr(substring as String) as Integer
vs
Instr(start_index as Integer, substring as String) as Integer

This is the worst case, because it doesn't conform to the brightscript function pattern.

Also see:

• Mid(start_index as Integer) as String vs Mid(start_index as Integer, num_chars as Integer) as String
• StartsWith(matchString as String) As Boolean vs StartsWith(matchString as String, matchPos as Integer) As Boolean
• EndsWith(matchString as String) As Boolean vs EndsWith(matchString as String, length as Integer) As Boolean

In these cases, the 2nd param can basically be thought of as optional

[markwpearce]

This is also a problem/issue for ifSGNodeFields with overloaded methods observeField and observeFieldScoped

[markwpearce]

Can probably be mitigated in the ScopeValidator by checking function calls against UnionTypes and validating if the call does not meet either signature...