https://issues.dlang.org/show_bug.cgi?id=24374
--- Comment #2 from Derek Fawcus <dfawcus+dl...@employees.org> --- I should modify that comment, I see that I can work with betterC despite the inability to mark the C imports as @nogc etc, as long as I haven't marked the betterC code in that fashion. So that was an error on my behalf, and I can continue investigating the viability of betterC additions to existing C code. I suspect this means not being able to optimise the repeated import of a common C header/module across multiple betterC file, in that each will have to parse the C source each time. --
