[XLS] Add a more-precise model of OneHot for IntervalSets #2227
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.
[XLS] Add a more-precise model of OneHot for IntervalSets
Rather than converting our IntervalSets to ternary values, trying to model the impact of
one_hot
there, then converting back with poor resolution - we instead test if each possible result bit can be set, and add it to our resulting IntervalSet if it can.NOTE: The runtime performance of this should be
O(I*n^2)
, whereI
is the number of intervals in the inputval
, andn
isval.BitCount()
, sinceCoversTernary
runs inO(I*n)
time.