Revert "Anywhere is not supported by the haskell backend (#2998)"#3041
Merged
rv-jenkins merged 1 commit intodevelopfrom Nov 14, 2022
Merged
Revert "Anywhere is not supported by the haskell backend (#2998)"#3041rv-jenkins merged 1 commit intodevelopfrom
rv-jenkins merged 1 commit intodevelopfrom
Conversation
This reverts commit 8e519d6.
Baltoli
requested review from
dwightguth,
ehildenb,
mariaKt,
radumereuta and
theo25
and removed request for
mariaKt
radumereuta
approved these changes
Nov 14, 2022
6 tasks
Baltoli
added a commit
that referenced
this pull request
Nov 18, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The C semantics is currently unable to update to the latest K version because of an issue with this PR; we have several
anywhererules that throw false-positive errors because of how we split our semantics into translation / execution phases.I think the best thing here is for the original change to be reinstated with a flag to disable this check for users who want to self-certify they'll never write an
anywhererule that gets reached by the Haskell backend. For now it would be good to revert this change so that we can fix our CI.