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

Type inference and updates #110

Open
Skepfyr opened this issue Oct 7, 2019 · 0 comments
Open

Type inference and updates #110

Skepfyr opened this issue Oct 7, 2019 · 0 comments
Labels

Comments

@Skepfyr
Copy link
Contributor

Skepfyr commented Oct 7, 2019

If at any point you or someone else has implemented any form of type inference, automatic type updates, or large scale type checking, then it is worth considering that it could replace the current store of each operations type. Most operations perform simple type-level manipulations of input to output, so module/function level type inference is feasible. It was deemed simpler to keep the type of each operation inline, however, any code that performs this sort of function could change this calculus so it should be reconsidered.
Supersedes #103, see that for extra context.

@Skepfyr Skepfyr added the tracker label Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant