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

Make an RFC for embedding types, contracts, and other specifications #9

Open
jeapostrophe opened this issue Jul 14, 2019 · 2 comments

Comments

@jeapostrophe
Copy link
Collaborator

jeapostrophe commented Jul 14, 2019

A key idea, for me, is to be able to separate specifications from the code that uses them, so multiple modules can use the same specification. Here specification is types, contracts, tests, theorems that are true about the software, and so on.

@samdphillips
Copy link
Contributor

Can you see this as a mechanism to compile code without contracts?

@jeapostrophe
Copy link
Collaborator Author

Yup. My perspective is that we should write down very expressive specifications (theorems and contracts with lots of dependencies and precision) and be able to smoothly compile them in a variety of policies from full enforcement and testing to no-seatbelts-or-helmets.

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

2 participants