ExactGlobe::adjacency does contain duplicate edges despite what documentation says.

[VictorElHajj]

"The output will not contain duplicate edges but no other guarantees are made."

I'm using this wonderful crate for a bevy project (thanks for the bevy example!) and I ran into an issue building my face connection graph, a lot of faces seem to have duplicate edges. For example (ExactGlobe::<31>::new()) I get these edges:

[(41, 0), (71, 0), (101, 0), (131, 0), (161, 0), (161, 0), (41, 0), (71, 0), (101, 0), (131, 0)]

There are 10 edges containing face 0 with duplications like (41, 0), (0,41).

Another example I got is
[(41, 0), (71, 0), (101, 0), (131, 0), (161, 0), (161, 0), (41, 0), (71, 0), (101, 0), (131, 0)]

In this case there were also duplicates with the same order on the faces (41, 0), (41, 0)

I looked at the other closed issue and saw that you decided to co-operate on subsphere, is this crate still being worked on? I tried that other crate but it was missing the convenient mesh methods you had which made my life much easier :)

[MorganBennetDev]

Thanks for the issue! Glad to see someone's using this. I should definitely update the README with the status of the project, which in short is: this library is feature-complete for what I needed it for so I will not be adding new features but I will do bugfixes. I will look into your issue and try to get a fix out this week.

Subsphere is intended to be a lower-level and more general purpose spherical tessellation library than this so it won't include a lot of the nice utility methods in Hexglobe. I am currently working on porting over some of the Hexglobe code to Subsphere so it might be worth turning Hexglobe into a higher-level wrapper library at some point but we'll see.

[VictorElHajj]

Thanks for the explanation! I've worked around it by manually de-duplicating, so no rush on my side.