Add function type info#281
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Objective
Add function type information support to the reflect module, enabling the reflection system to track and query function parameter and return types.
Solution
Introduced a new
FunctionInfoclass that extendsTypeInfoto store function signature metadata. This class provides:TypeIdTypeIdAdditionally, added a
typeidFunctionutility that generates proper type IDs for function signatures in the formatfn(param1,param2,...):returnType.Extended the type system by adding the
TupleFnConstructortype definition to properly represent parameter type tuples in a type-safe manner.Showcase
Migration guide
No breaking changes. This is a pure enhancement to the reflect module that adds new functionality without modifying existing APIs.
Checklist