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

Update implementation for int_vector branch of bit_vector #18

Merged
merged 2 commits into from
Aug 12, 2018

Conversation

leonardt
Copy link
Owner

@leonardt leonardt commented Aug 2, 2018

No description provided.

@leonardt
Copy link
Owner Author

leonardt commented Aug 2, 2018

Tracking leonardt/hwtypes#8

@coveralls
Copy link

coveralls commented Aug 2, 2018

Pull Request Test Coverage Report for Build 117

  • 33 of 34 (97.06%) changed or added relevant lines in 6 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.8%) to 77.282%

Changes Missing Coverage Covered Lines Changed/Added Lines %
fault/tester.py 4 5 80.0%
Totals Coverage Status
Change from base Build 115: 0.8%
Covered Lines: 381
Relevant Lines: 493

💛 - Coveralls


def __check(self, sim_val, expected_val):
if expected_val is None:
# Expected None, skipping
Copy link
Collaborator

Choose a reason for hiding this comment

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

should we print some warning in this case? why would expected_val be None?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I believe we are using None to mean any value. This seems likely to cause problems in the future.

Copy link
Owner Author

Choose a reason for hiding this comment

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

Perhaps we could use some object called Any? Basically, we need a way of specifying in a testvector to not check an output value. The idea with None is if that "There is no expected value". An Any object could also work: it can be any value.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Seems like a good idea. As long as it doesn’t confuse ppl with the generic type construct Any. Perhaps AnyValue?

Copy link
Owner Author

Choose a reason for hiding this comment

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

Updated to use AnyValue

@leonardt leonardt merged commit f8413f4 into master Aug 12, 2018
@leonardt leonardt deleted the int_vector branch August 12, 2018 00:53
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

Successfully merging this pull request may close these issues.

None yet

4 participants