Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

better support for concrete methods #391

Open
bakkot opened this issue Dec 13, 2021 · 2 comments
Open

better support for concrete methods #391

bakkot opened this issue Dec 13, 2021 · 2 comments

Comments

@bakkot
Copy link
Contributor

bakkot commented Dec 13, 2021

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.

@bakkot
Copy link
Contributor Author

bakkot commented Dec 16, 2021

Maybe internal methods, too.

@jmdyck
Copy link
Contributor

jmdyck commented Feb 15, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants