Open josephmoresena opened 2 weeks ago
The ability of consuming C# code in VB is already broken since C# 7.2. Here's a list of interoperability issues of calling C# library with VB (found in my projects):
ref struct
(Span(Of T)
, Utf8JsonReader
)ref readonly
returns (ReadOnlySpan(Of T).Item
)in
parametersref readonly
parametersunmanaged
constraint (ImageSharp, OpenCVSharp)record
typesIAsyncEnumerable
IAsyncDisposable
objects with Try ... Finally
Parallel.ForEachAsync
)allows ref struct
constraintinit
properties@Nukepayload2 are these is the Roslyn Repo? Does on the team actually look here anymore? Give the goal of keeping VB compatible with C# libraries all of these should be bugs.
I am trying to implement an interface created in a C# assembly in .NET 8, which has both static virtual and abstract members. However, it's not possible to implement this interface in a Visual Basic class because all interface implementation methods have to be instance methods, and when I try to compile, it indicates that the method does not match the interface.