Tanner Gooding

The new `static abstracts in interfaces` feature is enabling the libraries to expose support for generic operators. The API surface and design work for that is here: https://github.com/dotnet/designs/pull/205

Its just an automatically imported `props` file and one that the IDE tooling knows how to reference and handle. You can put anything in it and can even put `PackageVersion`...

Could you provide more information about the terminal you're using? This seems like a bug there and that its trying to automagically resolve and register command line options for `libClangSharp.so`...

(Of course this could be a compilation issue or something trivial to resolve on my end, so details would help resolve this 😄)

Seems like its missing from the tool package. I'll work to get a v15.0.1 patch up. I expect the `PrivateAssets` on the package is incorrect.

Fixed with v15.0.1 now on NuGet.

@ygc369, there is already a championed proposal for extending `fixed-sized-buffers` to support arbitrary types (see https://github.com/dotnet/csharplang/blob/master/proposals/fixed-sized-buffers.md).

The raw bindings () and minimal wrapper API () should be stable and could be published as a 10.0.0 package. The proper managed wrapper (such as , however is not...

> Raw could be LLVMSharp.Interop and managed wrapper could be LLVMSharp.Managed. Yes, that could be a possibility. Although I think `LLVMSharp` and `LLVMSharp.Interop` might be better. > Apologies for my...

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 (minus...