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.

Sign up for GitHub

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

Jump to bottom

Type expressions should change with context #15

Open
CodyFagley opened this issue Nov 19, 2019 · 0 comments
Open

Type expressions should change with context #15

CodyFagley opened this issue Nov 19, 2019 · 0 comments
Labels
prebug Not a bug yet, but will be soon

Comments

@CodyFagley
Copy link
Member

When a function or parameter is used in a valid, more-restrictive context, the node's type expression should reflect the matching type expression.

Each node should start as TYPE_ARBITRARY until a more restrictive type expression is enforced. Each node's type expression should be as generalized as possible for a given circumstance.
@CodyFagley CodyFagley added planning Groundwork for further work prebug Not a bug yet, but will be soon and removed planning Groundwork for further work labels Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
prebug Not a bug yet, but will be soon
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CodyFagley