[–] skulk 5mo ago ↗ Interesting use of macros to get a generic "result" thingy:https://git.sr.ht/~willowf/beebo/tree/master/item/src/result...I think it's cool that stuff like this works in C but my gut feeling is that this isn't going to play well with LSP tools. Are state-of-the-art C LSP servers aware of the preprocessor? [–] whou 5mo ago ↗ yes, C LSP servers can deal with the preprocessor just fine, even the trickier C preprocessor "hacks". clangd is built on top of clang, after all. [–] anon25783 5mo ago ↗ I'm using a current version of VS Code with the IntelliSense mode set to `linux-gcc-x64` and it seems to work quite well actually.
[–] whou 5mo ago ↗ yes, C LSP servers can deal with the preprocessor just fine, even the trickier C preprocessor "hacks". clangd is built on top of clang, after all.
[–] anon25783 5mo ago ↗ I'm using a current version of VS Code with the IntelliSense mode set to `linux-gcc-x64` and it seems to work quite well actually.
5 comments
[ 2.8 ms ] story [ 29.0 ms ] threadhttps://git.sr.ht/~willowf/beebo/tree/master/item/src/result...
I think it's cool that stuff like this works in C but my gut feeling is that this isn't going to play well with LSP tools. Are state-of-the-art C LSP servers aware of the preprocessor?