-
Notifications
You must be signed in to change notification settings - Fork 6
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
Use upstream's Sprite annotations (/*@...*/
)
#266
base: pure-z3
Are you sure you want to change the base?
Conversation
This makes it easy to cross-check examples with upstream Sprite.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we are already here, focusing our attention on properly parsing the upstream /*@...*/
annotation syntax, why not go all the way and remove ⟦...⟧
, (changing the tests of course), this way we are char-for-char identical to the upstream? I recommend focusing on one topic per PR. This particular change would be named something like "Use upstream Sprite annotation syntax (/@…/)", and cherrypick this commit, change the tests, and remove the ⟦...⟧
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get it. Are you suggesing to depart from the upstream syntax here?
In upstream, if an id starts with uppercase, you know it's either a data constructor (see how ctorP
calls cbind
in Parse.hs
), or a switch-case (altP
in Parse.hs
).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, how is this any different? I am looking at #word
and it is PPCharSetPredicate
on isAlphaNumeric
, which is just isLetter or: [isDigit]
, no?
OK, no problem.
Yes.
Ah, my bad. IIRC this has not been so in the early versions of PP, will drop that change. |
06a90d6
to
15e5aab
Compare
/*@...*/
)
Forget it, I'll deal with that differently some time in the future. |
Ok, this is excellent. Now the next question is how to merge such things. Because if we merge into |
We can drop last commit (removing support for [[ ]]) and add it later, once the rest is merged, or the other way round, Up to you. |
This PR scratches the worst of my itches when writing Sprite by hand. Still, there's more to fix (#193 and things I already forget)