[Proposal]: Separate Vertex, Edge, Loop, and Face in to their own files about bmeshunity HOT 3 CLOSED

Maybe the best way to minimize the fix required by breaking changes would be to put all classes in a namespace called BMesh. This way BMesh.Vertex remains valid, using static BMesh can be changed into using BMesh when one uses it.

So feel free to PR such a change, I'll be happy to merge it and have this code be more idiomatic!

from bmeshunity.

Maybe the best way to minimize the fix required by breaking changes would be to put all classes in a namespace called BMesh. This way BMesh.Vertex remains valid, using static BMesh can be changed into using BMesh when one uses it.

So feel free to PR such a change, I'll be happy to merge it and have this code be more idiomatic!

I think a namespace is a good idea, but doing so just moves the breaking change to people that use using static BMesh, naming the namespace BMesh also invalidates any the direct references to the BMesh class such as BMesh mesh = new BMesh(), so perhaps a different namespace name? Or just none at all?

from bmeshunity.

Let's call it BMeshUnity then. And yes we will break things anyways. As a transition measure, we can add a public alias Vertex = BMeshUnity.Vertex in BMeshUnity.BMesh (idk if the keyword using makes it a public alias, otherwise we can define a derived class public class Vertex : public BMeshUnity.BMesh {}.

from bmeshunity.