Allow lookups of overloaded methods. #5110
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FunctionReflection*
to be either aDeclRefBase*
(unique function) or anOverloadedExpr*
(multiple candidates)FunctionReflection*
except forspecializeWithArgTypes
will fail & returnnullptr
if it is overloadedisOverloaded() -> bool
,getOverloadCount() -> unsigned int
andgetOverload(unsigned int) -> FunctionReflection*
can be used to cycle through candidatesFunctionReflection::specializeWithArgTypes
can be used to resolve to a single function, based on argument types by using invoke resolution, This will also perform generic argument inference where necessary.Breaking Change Notes:
Previously, the result of
findFunctionByName
andfindFunctionByNameInType
returnnullptr
if the function is overloaded. They will now return a non-null pointer, but they cannot be used with most function-reflection methods without resolving to a unique function. Users should callFunctionReflection::isOverloaded()
to decide if the returned function reflection is useful.Fixes #5090