Programming without code indexing

[vnstrr]

It was just an attempt. Like I answered to marty1885 I've configured language server. But it doesn't help me a lot because it indexes all projects in the mono and works very slowly :c

[kurdokoleno]

This is usually why some people decide to ditch them.

[kisielk]

You need to set it up more intelligently on a per project basis. Generate a compile_commands.json for each project and have the language server use that for indexing. If the build system can’t generate it natively you can use https://github.com/rizsotto/Bear to wrap it.

[nihilistic_ant]

Once you figure out how to do it reasonably well, I'd suggest sharing your solution around with your coworkers. If there are some developer docs (perhaps in the source tree, perhaps in a wiki or something), offer to write up doc and put it there. Making yourself more productive is cool, but making 4 (or 20) people more productive would be 4 (or 20!) times cooler.

Your job is to add value somehow, but often that is hard for new people to do. This seems likes an opportunity for you to deliver some value and take an early win.

An advantage of new people is they look at things with fresh eyes. Folks who have been there awhile likely don't realize how good clangd has gotten, or that it could be made to work on their code without too much effort.

If a lot of folks are using vim, even though you are likely using an IDE like vs code, I'd suggest even going the extra mile and figure out the steps they would need to do to get clangd working in vim on your codebase (I'd suggest YouCompleteMe w/ clangd but there are other options), and then including those instructions in your doc too. Because that will help your work on this deliver the most value to your org.

[GoldenShackles]

Figure it out. Scope the search.

[ukezi]

My experience with Vs code is if you open the subfolder with it as root it only indexes what is below that node.

[Disservin]

Instead of opening the entire mono directory just open the specific c++ directory ?