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

When looking for matches for holes, prefer local bindings over top-level/in-scope module binding #1193

Open
dhess opened this issue Nov 30, 2023 · 0 comments
Assignees
Labels
blocked/need-info ❌ Blocked, need more information enhancement New feature or request UX UX issue

Comments

@dhess
Copy link
Member

dhess commented Nov 30, 2023

We suspect that in most cases, when inserting a value into a hole, the student will want to use a local binding whose type matches the hole, in favor of any top-level or in-scope module binding that also matches; so we should probably implement this in the partial sort of offered bindings (aka "variables").

(Note that it may be the case that we already do this, but I'm creating this issue as a reminder to check, at the very least.)

@dhess dhess added enhancement New feature or request blocked/need-info ❌ Blocked, need more information UX UX issue labels Nov 30, 2023
@dhess dhess self-assigned this Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/need-info ❌ Blocked, need more information enhancement New feature or request UX UX issue
Projects
None yet
Development

No branches or pull requests

1 participant