fix bool branch interpretation - #102
Merged
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #102 +/- ##
==========================================
+ Coverage 88.17% 88.19% +0.01%
==========================================
Files 11 11
Lines 1328 1330 +2
==========================================
+ Hits 1171 1173 +2
Misses 157 157
Continue to review full report at Codecov.
|
Moelf
reviewed
Sep 15, 2021
Co-authored-by: Jerry Ling <proton@jling.dev>
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
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.
We needed a specialized case to interpret boolean branches as
Vector{Bool}instead ofBitVector. I factored out the solution and unit test from #95 .before
💥🚗
after