You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|**COM and `IUnknown`**| ✔️ |<xref:System.Runtime.InteropServices.ComWrappers><xref:System.Runtime.InteropServices.Marshalling.GeneratedComInterfaceAttribute><xref:System.Runtime.InteropServices.Marshalling.GeneratedComClassAttribute>|
|**COM and `IUnknown`**| ✔️ |<xref:System.Runtime.InteropServices.ComWrappers><xref:System.Runtime.InteropServices.Marshalling.GeneratedComInterfaceAttribute><xref:System.Runtime.InteropServices.Marshalling.GeneratedComClassAttribute>|
The [C++ language](https://isocpp.org/) has no defined ABI across all .NET supported platforms and C++ compiler implementations (that is, MSVC, clang, and GCC). This lack of a stable ABI makes support difficult to provide. The recommended way to interoperate with C++ is to export functions marked with `extern "C"` and then call them as C functions.
23
23
24
-
## golang <aname="golang"></a>
24
+
## <aname="golang"></a> golang
25
25
26
26
The Go programming language is not supported for in-process interoperability. The Go runtime [imposes requirements](https://pkg.go.dev/os/signal#hdr-Non_Go_programs_that_call_Go_code) on being hosted in a process with another run time. Specifically, the use of the `SA_ONSTACK` flag on threads that run signal handlers. These requirements are not currently met by .NET and meeting them would impose non-trivial costs.
27
27
28
-
## ARM64EC <aname="arm64ec"></a>
28
+
## <aname="arm64ec"></a> ARM64EC
29
29
30
-
The [ARM64EC](https://learn.microsoft.com/cpp/build/arm64ec-windows-abi-conventions) ABI is not supported.
30
+
The [ARM64EC](https://learn.microsoft.com/cpp/build/arm64ec-windows-abi-conventions) ABI is not supported.
0 commit comments