Moritz Mœller

That sounds like a very neat option that saves me lots of code! Thanks heaps.

Wouldn't this more ergonomically expressed like this though: ```cpp libfive_tree libfive_tree_clone(libfive_tree ptr) { libfive_tree clone = ptr; Tree(clone).release() return clone; } ```

I got everything working now. One thing I have done so far is use functional style since that is more idiomatic (i.e. `5.0.sin()` is what `sin(5.0)` looks like in Rust):...

I just published [this on crates.io](https://crates.io/crates/libfive).

Yes, absolutely. DC seems to give the best meshes for this use case anyway.

I.e. the docs could mention this but ultimately it would the user's decision. That being said: is it possible to switch the meshing method via Scheme or only through the...

Non-planarity is a non-issue. Particularly if those meshes are used as base shapes for render time subdivision surfaces.

The best reference is [this](http://paulbourke.net/dataformats/obj/). A copy of the original format description from Wavefront. Vertex normals are useful. They can be used to discover which edges to tag as [creases](https://graphics.pixar.com/opensubdiv/docs/subdivision_surfaces.html#semi-sharp-creases)...

I am more interested in obtaining a mesh in memory from the lib. So I see two options: 1. I can add the `quality` knob to all functions in the...

[I went ahead with 2.](https://github.com/virtualritz/libfive/commit/c414cb31f43c21da626d6820c0657f7237d61330) and mirrored the C API so far: ```c typedef enum libfive_brep_alg { DUAL_CONTOURING, ISO_SIMPLEX, HYBRID, } libfive_brep_alg; typedef struct libfive_brep_settings { /* The meshing region...