Could this library benefit from C++/CLI?

[nikeee]

We could probably write the C++-wrapper in C++/CLI. If that would be the case, we wouldn't need any p/invokes for accessing that from C#. We could just reference that directly.

Some refs:

• https://stackoverflow.com/questions/1433334/performance-differences-between-p-invoke-and-c-wrappers
• https://www.red-gate.com/simple-talk/dotnet/net-development/creating-ccli-wrapper/

Maybe there are other things like C#9's function pointers that could enhance performance.

[nikeee]

dotnet/core#4975 (comment)

It's legacy technology. So don't opt-in for that.

[nikeee]

Maybe C#9's function pointers?

If this p/invoke source code generators?
dotnet/runtime#43060
https://github.com/dotnet/runtime/blob/main/docs/design/features/source-generator-pinvokes.md

They maybe they will be part of the compiler, so we won't need to change anything to benefit from this?

But, however, this is important:

Ability to innovate in support of modern .NET types (e.g., ReadOnlySpan/Span).

If they support Span<T> in p/invokes, it would be a game changer (currently, this is not supported because generics cannot be marshalled in general).

Also:

Non-Goals:
Zero code change for the developers.

So we might need to change something.