Moritz Mœller

Yeah, I get it. I wrote a `gen_rust.py` and there I have the issue with `move` (Rust keyword). I swap that out for `moveit`.

What I have done in my fork is to prefix every function in `stdlib.h` with `libfivestd_`. I also changed the `gen_c.py` to do the right thing already. I.e. generated files...

+1

For recursive evaluation I'd have to make a whole new API for the crate that executes the geometric operations. It uses the builder pattern which mirrors how people think about...

Good overview: https://blog.krzyzanowskim.com/2018/12/05/rpath-what/

You also need 4D when you have 3D solid noise on some 3D geometry and you want to animate/change this over time. In such cases you point sample the noise...

I'm not comfortable submitting a PR until #70 is resolved. In general, I think it would give users confidence if the original TA-lib test data was used to verify all...

I have the same issue on my [`opensubdiv-petite-sys`](https://github.com/virtualritz/opensubdiv-petite/tree/master/opensubdiv-petite-sys) wrapper when building on Linux (Ubuntu 22.04). It does indeed go away if I link against `libc++` but I would very much...

> [...] So linking against `libc++` to work around this bug means no docs.rs documentation. Bummer, it does indeed. I just published an update to my crate and the docs...

I'm getting this error on Ubuntu 23.04 with `bandwhich` v0.20.0 installed via `cargo`. No VM. I'm connected and I do not have a VPN running. My `resolv.conf` looks like this...