You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The notation I use for reasoning about API designs is based on PistonDevelopers/piston#736. This notation has the benefit that it can express path semantics between functions without needing to encode that information into the types, so it is very easy to use for reasoning.
I have tested piston-meta by writing the rules manually and think it also would serve as a good test case for testing bootstrapping meta rules. With bootstrapped rules, we would have a better guess if there is a good idea to share a meta language across libraries. The bootstrapped rules for the mathematical notation could also open up possibilities for further research projects.
The text was updated successfully, but these errors were encountered:
The notation I use for reasoning about API designs is based on PistonDevelopers/piston#736. This notation has the benefit that it can express path semantics between functions without needing to encode that information into the types, so it is very easy to use for reasoning.
I have tested piston-meta by writing the rules manually and think it also would serve as a good test case for testing bootstrapping meta rules. With bootstrapped rules, we would have a better guess if there is a good idea to share a meta language across libraries. The bootstrapped rules for the mathematical notation could also open up possibilities for further research projects.
The text was updated successfully, but these errors were encountered: