Thank you!

[psznm]

I am really happy I have found this repo, because it solves exactly the issues with zls that made me want to fork it myself. I only learned of zigscient because I learned of reasons for some of the issues of zls by trying to improve it. I think it is a shame this project is not more visible, because I feel the improvements made are worth it.

On another note, I am looking for something to do with my free time. Thinking of adding some new code actions. If I do, its probably better to develop and add PR on zls since you regularly pull from it?

[llogick]

I am really happy I have found this repo, because it solves exactly the issues with zls that made me want to fork it myself. I only learned of zigscient because I learned of reasons for some of the issues of zls by trying to improve it. I think it is a shame this project is not more visible, because I feel the improvements made are worth it.

Welcome :)

On another note, I am looking for something to do with my free time. Thinking of adding some new code actions. If I do, its probably better to develop and add PR on zls since you regularly pull from it?

I'd say that, yes, when it comes to common/shared sections of the codebase contributions made upstream would be best.

In general, I'm not looking to add too much code/features until we figure out the parser and redesign everything around it.

P.S. Did you see https://github.com/llogick/zigscient-next ? I could use feedback on that one as well.

[psznm]

zigscient-next looks awesome. Will give it a try!