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

state variables should not have syntax restriction and s/be multiformat strings #361

Closed
michaelcfanning opened this issue Apr 8, 2019 · 0 comments

Comments

@michaelcfanning
Copy link
Contributor

The point of state variables is that they display some usable information re: conditions at various points in the code flow. These may be simple values or they may be constraints, assumptions, invariants, etc.

We should accordingly remove the current restriction that these items must conform to a specific language's syntax. Since they are open-ended ('display useful information re: state'), users should have the flexibility moving forward of using markdown to express them.

@ghost ghost self-assigned this Apr 8, 2019
ghost pushed a commit that referenced this issue Apr 8, 2019
@ghost ghost added the resolved-fixed label Apr 8, 2019
@ghost ghost closed this as completed Apr 8, 2019
@ghost ghost added the merged Changes merged into provisional draft. label Apr 9, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant