How does D compare to Go when it comes to C interop?

[John Colvin via Digitalmars-d]

On Thursday, 10 December 2015 at 14:57:33 UTC, Jack Stouffer 
wrote:
> On Thursday, 10 December 2015 at 13:52:57 UTC, John Colvin 
> wrote:
>> On Thursday, 10 December 2015 at 13:33:07 UTC, Pradeep Gowda 
>> wrote:
>>> 5. Debugging (ease of accessing C parts when debugging)
>> 5) Trivial. From the debuggers perspective it's all just 
>> functions, you might not even notice the language barrier. All 
>> D debuggers are also C debuggers and I doubt that's going to 
>> change.
>
> To add to this, as long as you're on anything but OS X, you're 
> fine. Debugging D on OS X is, to put it plainly, fucked.

Never had any real problems with it, but I don't expect much from 
my debuggers. Breakpoint, backtrace, disassemble, register dump. 
Maybe some stepping about once a year.