ImportC: On the issue of using a type from two different C files

[Paul Backus]

On Saturday, 27 August 2022 at 03:07:25 UTC, Mike Parker wrote:
> Martin disagreed, and proposed an alternative:
>
>> Martin said that one problem with that approach is that a D 
>> module would have access to symbols it didn't import. He 
>> suggested the ideal solution would be for each header to have 
>> its own module that doesn't change from one invocation of the 
>> compiler to the next.

This pretty much requires DMD to incorporate a C preprocessor, 
right? Since that's the only way it can reliably determine which 
headers are included.