-
Notifications
You must be signed in to change notification settings - Fork 1
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
operators and arities #2
Labels
Comments
This was referenced Jul 7, 2016
Closed
Closed
this might also let us restate the action semantics that makes fewer proof cases? like instead of zip1, zip2 etc, index them by fin4 or whatever. |
from the old todo:
|
yeah, i think i agree. |
migrating this to the issue tracker repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
reformulate things in terms of 312-style-ish operators and arities. this should mean that case is easier to state, movements to children can be done with
Fin (arity oper)
rather than ad hoc hoping to pick the right indices, and a bunch of rules can be combined. at the least, the ap and plus rules would get combineddo this for types, too---as evidenced by thinking about adding sums, the same problems exist there. and really, that's why 312 uses the same ABT functor for types as well as terms.
The text was updated successfully, but these errors were encountered: