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 inference for expressions #61

Closed
brendanzab opened this issue Nov 29, 2017 · 1 comment
Closed

Type inference for expressions #61

brendanzab opened this issue Nov 29, 2017 · 1 comment
Labels
A-type-system C-enhancement E-medium
Projects
Development

Comments

@brendanzab
Copy link
Member

brendanzab commented Nov 29, 2017 •
edited

We might need some simple type inference at the expression level. For example when numeric suffixes are left off, or for empty array literals, variant introduction, etc.
@brendanzab brendanzab added this to Backlog in Development Nov 29, 2017
@brendanzab brendanzab moved this from Backlog to In Progress in Development Jan 15, 2018
@brendanzab brendanzab mentioned this issue Jan 15, 2018
Merged
@brendanzab brendanzab moved this from In Progress to Ready in Development Jan 18, 2018
brendanzab added a commit that referenced this issue May 1, 2018
@brendanzab
Merge pull request #61 from brendanzab/im
9b15932 
Switch to im for our persistent vector needs
@brendanzab
Copy link
Member Author

This was fixed when we merged in the Pikelet code base, with its bidirectional type checking!

Development automation moved this from Ready to Done Jun 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-type-system C-enhancement E-medium
Projects
Development
  
Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brendanzab