-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[move] Remove spec
syntax and ignore new-style specs
#20687
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
spec
syntax and ignore new-style specs
Thanks! Could we get another run? |
@cos do I understand it correctly that this is only the change that you would like to upstream to the main repo to push your code to the move nursery? |
This reverts commit 2fa0ace.
@dariorussi yes, these are the only changes -- we might follow up with a minor PR in case we missed something. Just pushed again, fixed a bug and renamed "verify" to "spec" to reduce any confusion with signature verification. |
Description
spec
andinvariant
keywords, and associated data structures.test_only
, but more extensive, covering system code as well.See this test and other files in the same directory for examples of filtered out code.
Test plan
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.