On 7/6/19 3:26 AM, Aldy Hernandez wrote:
>
>
> On 7/3/19 7:12 PM, Jeff Law wrote:
>> On 7/1/19 4:24 AM, Aldy Hernandez wrote:
>>> This is completely unrelated to range-ops itself, but may yield better
>>> results in value_range intersections. It's just something I found while
>>> working on VRP,
On 7/3/19 7:12 PM, Jeff Law wrote:
On 7/1/19 4:24 AM, Aldy Hernandez wrote:
This is completely unrelated to range-ops itself, but may yield better
results in value_range intersections. It's just something I found while
working on VRP, and have been dragging around on our branch.
If we know t
On 7/1/19 4:24 AM, Aldy Hernandez wrote:
> This is completely unrelated to range-ops itself, but may yield better
> results in value_range intersections. It's just something I found while
> working on VRP, and have been dragging around on our branch.
>
> If we know the intersection of two ranges
This is completely unrelated to range-ops itself, but may yield better
results in value_range intersections. It's just something I found while
working on VRP, and have been dragging around on our branch.
If we know the intersection of two ranges is the empty set, there is no
need to conservat
