Nick Strupat

I have working some basic support for complex types, including nested complex types in my fork. It broke a couple unit tests and doesn't seem to work in my larger...

Something like this ```csharp public class Foo { [JsonProperty(Required = Required.Always)] [OneOf(typeof(Baz), typeof(Faz), typeof(Waz))] public Object Bar { get; set; } [JsonProperty(Required = Required.Always)] [MinLength(1)] [AnyOf(typeof(Baz), typeof(Faz), typeof(Waz))] public Object[]...

Oh my, does that work already?

So the `KnownTypeAttribute` constructor only takes one `Type`, but it does allow multiples instances of that attribute. Per-property specification of `oneOf`, `anyOf`, `allOf`, and then the negation of those (`not`)...

Have you looked at the LSP server inside ClangD? I'm looking at using it as well, assuming it's good enough as it's part of LLVM. https://github.com/llvm/llvm-project/blob/main/clang-tools-extra/clangd/ClangdLSPServer.h

Would this mean one package for raw bindings and one package for managed wrappers? Raw could be `LLVMSharp.Interop` and managed wrapper could be `LLVMSharp.Managed`. Apologies for my confusion, but it...

Ok thanks. I'll take a look at the C++ bindings to get some more context. A bit of a tangent, but have you looked at using ClangSharp to consume the...

> I personally don't like the idea of two assemblies for essentially the same functionality. It is sort of expected that the LLVM C APIs are somewhat stable, but not...

> The raw bindings are auto-generated and since they are generated as 1-to-1 they should always be "correct" and therefore are basically stable from the moment they are checked in...

Oh interesting... so if I specify a RID, I'll get the right libLLVM runtime along with my "published" output? That makes sense. I guess I assumed NuGet would bring all...