4 ms·
Note that the one feature holding this back from "true greatness" during development is that the tooling for providing LSP completions for D symbols in editors
by gavinray 4y ago
Note that the one feature holding this back from "true greatness" during development is that the tooling for providing LSP completions for D symbols in editors doesn't appear capable of detecting C code in your project yet
One of the major appeals of ImportC is that it does away with needing to write (and maintain) D bindings to C libraries -- by hand, or generated.
I was trying to experiment with io_uring in D and using liburing headers included in a C file + ImportC
My D app compiled and ran fine, and I could call liburing but in my editor I was in the dark as to what the methods I could call or their signatures were.
For hardcore vim programmers this is likely the norm, but for me I consider that a step backwards, and I went back to manually generating D bindings and using those.
Waiting for the day we'll see ImportC fully integrated into dub and pure-d/workspace-d!
- isthisthingon99 4y ago> For hardcore vim programmers this is likely the norm Just FYI, not anymore.