Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix(test): CheckBoundMatcher #1748

Merged
merged 1 commit into from
Nov 25, 2017

Conversation

pvojtechovsky
Copy link
Collaborator

I suggest to change this test, because the new template matcher (#1686), which collects matching parameter values, fails on this. Note: left and right expression are not same in the matching examples, so there should be different variables (x and y) and not only one, like it is now.

@monperrus
Copy link
Collaborator

I'm OK with this.

Could you add the test in 1686 showing that you match correctly x.S() == x.S() if the two expressions are the same?

Also, it would be great that you avoid in #1686 to modify existing test code for refactoring, so that we directly see the changed behavior (red lines in src/test) as opposed to new specification (green lines in src/test).

@monperrus monperrus merged commit a660024 into INRIA:master Nov 25, 2017
@pvojtechovsky pvojtechovsky deleted the fixCheckBoundMatcher branch November 26, 2017 09:25
@pvojtechovsky
Copy link
Collaborator Author

Could you add the test in 1686 showing that you match correctly x.S() == x.S() if the two expressions are the same?

Good idea, I will do.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants