You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea behind this ticket is to discuss the implementation of signatures that can be applied to types instead of functions.
The type signatures should match an specific amount of constraints in order to be selected as good candidates. F.ex:
Which fields are accessed its size and direction
Which functions takes them as argument
Alignment restrictions applied
Context with strings
Note that there's already some type inference support implemented by propagating only the types found in the function signatures. But there are more constrains that we can use in order to improve the quality of the autotyping as well as autonaming.
The idea behind this ticket is to discuss the implementation of signatures that can be applied to types instead of functions.
The type signatures should match an specific amount of constraints in order to be selected as good candidates. F.ex:
Note that there's already some type inference support implemented by propagating only the types found in the function signatures. But there are more constrains that we can use in order to improve the quality of the autotyping as well as autonaming.
Reference links:
The text was updated successfully, but these errors were encountered: