BooleanIntersection bug?

Just testing something else and I stumbled on this. Two overlapping volumes (say, boxes), preselect both, call BooleanIntersection and then hit Enter to just get the intersection of the two objects. V6 gives me the common intersecting volume of the two, in the WIP I get a Union instead… am I missing something?

BooleanIntersection Anomaly.3dm (373.9 KB)

No, you’re not missing anything. Someone fell into the C++ optional parameter coding trap. Thanks for the report.

RH-60579 is fixed in the latest WIP