Florian Jung

The problem is that this crate does really bad things such as panicking inside of an allocator. I'd rather use the `warn_debug` feature flag when testing and then use https://docs.rs/assert_no_alloc/latest/assert_no_alloc/fn.violation_count.html...

I've got another similar bug: ```py from build123d import * from ocp_vscode import * ZPOS=5 sphere = Location((0,0,ZPOS)) * Sphere(10) sphere.color = "#88ff8888" foo = project(sphere.faces(), workplane = Plane.XY) show(foo,...

Just looking into this. It appears to me that `project_to_shape` works by extruding the face-to-be-projected, and intersecting this extrusion with the target face. This has two issues: 1. I find...

for 1), I agree that there is no "correct" answer; however, what build123d currently does is hard to predict and highly unintuitive: It's not like we're projecting to the first...

a-ha! the missing `HasError` method [is pulled in via `using SomeProtectedBase::method`](https://github.com/CadQuery/OCP/blob/4b98a5dc79fa900f7429975708f6a8c2e41cecd1/opencascade/BRepAlgoAPI_Algo.hxx#L50) from a protected base class, and is not defined as a `bool normalMethod() { ... }`. Maybe this confuses...

Minimal example where this fixes something that was previously broken: ```py from build123d import * box = Location((0,25,0)) * Rot((10,10,10)) * Box(10,25,30) box2d = project(box.faces(), Plane.XZ) ``` however, i've seen...

_99 bugs in the code, track 1 down, patch one around, 182 little bugs in the code :/..._ So I found and fixed another issue, which fixed that failing test,...