Yingchi Long

I think @spikespaz 's solution is better and more clean, it seems like I don't need to integrate this into nixd itself. Agree? @nekowinston

Ironic thing: allowing arbitrary args were landed before. That's exactly legacy nixd. You can read more details at: https://github.com/nix-community/nixd/issues/471#issuecomment-2081332365

> I am a [readTree](https://github.com/tvlfyi/kit/tree/canon/readTree) user, so my repo consists of lots of files that are simple functions which accept arguments of my choosing. They look sort of like nixos...

> I would definitely be willing to accept stale completion info in exchange for better performance. Yes. That's actually work-in-progress. However: https://github.com/nix-community/nixd/issues/471#issuecomment-2081331297 > For a long time C++ part in...

> users.jenya = import ./home; Looks like you are using HM attributes in an nested `import`. It's generally hard to check this dataflow. (i.e. nixd cannot know `import`ed file will...

> My nix-darwin and home-manager configs are in separate files as well. Type hints in comment is a planned feature.

This is expected. Currently the parser gets stopped at the first token it cannot recognize indeed it should trigger some error, but not yet implemented, fixes might be available soon.

Thanks, any more ideas are welcomed!

> This also affects nixd however as its memory usage balloons to many dozen GiB when I do this. AFAIK my profiling data blames 'Document Symbol' for memory usage, for...

> If you can't disable just highlighting (that appears to be the primary performance limitation), can you disable eglot in certain paths only (or past a certain size)? Does it...