C# Bindings

[strich]

As discussed in #1173 (comment) I would be happy to commit our C# bindings (modified from https://github.com/weianweigan/manifold-csharp) to the project and begin the process of making it feature complete.
Are there a minimum set of requirements to getting a first pass in?

[pca006132]

I think we want to at least have a minimal CI setup so we can check for compilation error.

[elalish]

Agreed - and of course the real question with open source: will you stick around? I've never written any C#, and what we could really use are more collaborators.

[strich]

Agreed - and of course the real question with open source: will you stick around? I've never written any C#, and what we could really use are more collaborators.

Well of course I can't guarantee that. But bindings are hardly things that change a lot depending on what you folks have planned for Manifold. To me it makes sense to maintain at least a few key language bindings internally. I understand Python is popular with your userbase, and if we can bring C# up to scratch then you'll likely get a good influx of users from the gamedev industry through Unity support (implicitly).
I'd like to think any needed maintenance over time will be minor and possibly outsourced to devs like myself as they use it.

I may try to maintain, externally, a series of Unity tests as the data structure interop between Manifold and the Unity meshes it still something I haven't fully understood myself.

[elalish]

Sounds good to me - agreed that Unity would be another nice ecosystem to connect with.