Jérémie Dumas

We can leave an overload that uses a default-initialized RNG.

The reason is that other modules depend on other libraries, which makes exporting them properly with CMake more difficult, so it's not implemented yet. The recommended way to use libigl...

git submodules are horrible to use. We had that before, but downloading external content through cmake is much easier for the user (in CMake 3.11 it's called FetchContent). Our philosophy...

Btw if that's any consolation, the recommendation for production use is to [_compile everything at the same time with the same flags_](https://www.youtube.com/watch?v=IY8tHh2LSX4&t=1518). That means build everything from source with the...

There are solutions to translate SSE instructions to NEON, e.g. using https://github.com/DLTcollab/sse2neon or https://github.com/simd-everywhere/simde. But this would require adding additional dependencies to libigl, so imho we should move the `FastWindingNumberForSoups`...

No the upstream code is the same, but if we add the sse2neon dependency to the fast winding number code, I think we should do it in the upstream repository...

We could maintain it as a fork, like we do for triangle or tetgen. But jamming everything into a single header file and embedding it in libigl has several disadvantages....

FYI I have created a PR against the original WindingNumber code, adding support for M1 architecture via SIMDE: https://github.com/sideeffects/WindingNumber/pull/3

If you read my message above, you will see that I have a fork of the FastWindingNumber repository that works on M1: https://github.com/sideeffects/WindingNumber/pull/3 This work is not integrated in libigl,...

Yes there's an extra dependency which is [SIMDe](https://github.com/simd-everywhere/simde) (this does the translation of intrinsics). To use it just put these lines of codes in your CMake project: ```cmake include(FetchContent) FetchContent_Declare(...