Saleem Abdulrasool

@rauhul hmm, I think that the `@_implementationOnly import` are predating the `import` ACLs - the intent is to avoid leaking the imports into the clients, and as long as that...

> > The fatal error is related to the missing -parse-as-library due to the use of @main which is a long standing issue. > > Is this a windows specific...

@dabrahams no this behavior is not windows specific. The issue is reported by the frontend if you note. This really should be diagnosed on all platforms.

I suspect that there is something wrong with your setup. I was able to build this locally with the following: ``` compnerd.org Swift version 5.8-dev (LLVM 170e2cfa496ad7c, Swift f32ae6f8c6068cd) Target:...

@gregcotten hmm, and you aren't using C++ interop right? That would be incompatible.

What version of the Windows SDK are you using? I wonder if the interface changed at some point.

`reg` will let you query the registry from the command line. I'm not sure if there is a good solution here though :-(.

It works at least with 10.0.22621.0. Taking a look at d3d12.h from that version ... ```c typedef struct ID3D12CommandQueueVtbl { BEGIN_INTERFACE DECLSPEC_XFGVIRT(IUnknown, QueryInterface) HRESULT ( STDMETHODCALLTYPE *QueryInterface )( ID3D12CommandQueue *...

Are you sure that you are not getting some other header accidentally included as d3d12.h? I would run a verbose build and check the command line invocation.

o_O ... when did the API interface change? That would break all COM interfaces, because they expect a HRESULT. Could you test with the 10.0.22000.0 SDK? (Windows 11)