Júlio Hoffimann

@sjkelly we have ray-triangle intersection now. The algorithm was implemented by @HaoxuanGuo and it seems to be slightly faster than TriangleIntersect.jl. I've added the package to the list above and...

It is because in Julia it is not good practice to define methods for types that are not defined in the same module. It is called type piracy. We are...

@cdsousa we had some design iterations and thought that end users should see errors as early as possible with Integer coordinates. We assume that coordinates live in R^n, which is...

Definitely on topic 💯 I think we should document here in the issue the steps to achieve these goals. Currently I've been using PlyIO.jl, which is an excellent package to...

That is a great resource, thank you for sharing it. It will help other users while things get organized. On Wed, Dec 15, 2021, 05:22 Haoxuan Guo ***@***.***> wrote: >...

Contributions are very welcome Patrick, it would be awesome to have cohesive IO experience on top of the mesh types here. Are you planning to start the contributions with any...

I mean specific file formats like VTK and PLY. We currently have PlyIO.jl which is great for PLY files and could write other IO packages that read the meshes as...

So the idea is that all these backend packages only rely on native Julia arrays and dictionaries. The wrapper package MeshIO.jl will then depend on these backend packages to post-process...

Definitely! The promotion rule seems appropriate. We want to convert all Integer to Float64 to avoid errors downstream. Exact representaions willl demand a different abstract type that is not Integer.

@fujiwara-tofu-tm would you like to work on this issue?