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
I feel like this is already an open issue, but I couldn't find it, so making it again I guess.
We need to make concrete methods linkable and have some way to enforce that their signatures line up. Probably this means having a central place where the main definition lives, with (automatically generated) links to the various implementations.
The text was updated successfully, but these errors were encountered:
Probably this means having a central place where the main definition lives
This already exists. E.g., for the 3 HasBinding concrete methods, the 'central place' is in Table 16. For enforcing that signatures line up, the table declaration gives the number and names of the parameters, but not their types (or the return type). Or rather, that type info is mostly there in the "Purpose" column, but not in a way that can be easily extracted by code.
So are you thinking that the tabular forms would be replaced with structured-header forms?
I feel like this is already an open issue, but I couldn't find it, so making it again I guess.
We need to make concrete methods linkable and have some way to enforce that their signatures line up. Probably this means having a central place where the main definition lives, with (automatically generated) links to the various implementations.
The text was updated successfully, but these errors were encountered: