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

Should we be using = instead of equiv === on the spine? #85

Open
NicMcPhee opened this issue May 31, 2019 · 0 comments
Open

Should we be using = instead of equiv === on the spine? #85

NicMcPhee opened this issue May 31, 2019 · 0 comments

Comments

@NicMcPhee
Copy link
Member

At the moment we're using equiv (===) on the spine for equivalence/equality steps. It was suggested at a recent demo/feedback session that Gries & Schneider use "regular" equality (=) to indicate that the spine should be read as "A=B and B=C and C=D…" instead of in the associative manner of equivalence.

I should check the book (don't have one here), and if that's true (and it seems reasonable) we should change the checker to use this syntax.

@NicMcPhee NicMcPhee added this to the End of June, 2019 milestone Jun 1, 2019
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

1 participant