pub fn intersection_tris(a: &Mesh, b: &Mesh) -> Vec<Tri> ⓘExpand description
a ∩ b as the kernel’s own exact f64 triangles, WITHOUT the Mesh round-trip.
Mesh stores positions as f32, so intersection below loses ~1e-7 of
relative precision on the way out. That is irrelevant for a render buffer and
very relevant for anything that measures the result: on the analytic
rotated-box oracle the f64 triangles give exactly 9.375 m³ where the Mesh
round-trip gives 9.374999882. Callers that report a VOLUME (the clash
intersection solid, crate::clash_solid) take this entry; callers that only
need triangles to draw take intersection.
Empty on a #1109 budget trip, exactly like intersection.