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

Document the code/explain what is happening #1

Open
0x0f0f0f opened this issue Jul 1, 2020 · 0 comments
Open

Document the code/explain what is happening #1

0x0f0f0f opened this issue Jul 1, 2020 · 0 comments

Comments

@0x0f0f0f
Copy link

0x0f0f0f commented Jul 1, 2020

Im trying to read this together with the paper to reimplement this type system in go. Although the interpreter is simple, there are some things (like acronyms) that are not instantaneous to understand.
If you added some explanations of the internals in comments/github page it would be easier to reimplement and associate concepts/types/functions with the paper. Also, if you specified which rules are being applied in typecheck.ml it would also be a lot easier to associate pattern matching cases with the judgments in the paper.

For example, how are recursive functions achieved?

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

1 participant