Skip to content

Conversation

@ttuegel
Copy link
Contributor

@ttuegel ttuegel commented Jul 27, 2020


Reviewer checklist
  • Test coverage: stack test --coverage
  • Public API documentation: stack haddock

@ttuegel ttuegel added this to the Iteration 27 milestone Jul 27, 2020
@ttuegel ttuegel requested a review from andreiburdusa July 27, 2020 20:49
@ttuegel ttuegel mentioned this pull request Jul 27, 2020
2 tasks
:: HasCallStack
=> Ord variable
=> InternalVariable variable
=> [(SomeVariable variable, TermLike variable)]
Copy link
Contributor

@andreiburdusa andreiburdusa Jul 28, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see Ana left a "TODO" comment on line 431 about a posible refactoring. I could take care of it. What do you think @ana-pantilie @ttuegel ?
(I'm not able to comment on that line)

Copy link
Contributor

@ana-pantilie ana-pantilie Jul 28, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We already have unsafeWrapFromAssignments, and it looks like the major difference between these two is that unsafeWrap doesn't enforce the variable renaming invariant. I believe the question here is if we want to be able to create a Substitution like this, even for testing (where unsafeWrap is most widely used). @ttuegel what do you think? Is there any reason to keep unsafeWrap the way it is?

@rv-jenkins rv-jenkins merged commit a0aac45 into runtimeverification:master Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants