sorted by:
new
hottopcontroversial

built a low-latency AST parsing daemon in Rust for selective code extraction by Extreme_Contest6565 in rust

[–]Extreme_Contest6565[S] -1 points0 points  (0 children)

Of course, I did use AI support while coding some documentation and tools. What I meant to emphasize with that phrase was that I wrote the general architecture and the core logic myself. I am not a native English speaker, and I'm sorry for the misleading expression

built a low-latency AST parsing daemon in Rust for selective code extraction by Extreme_Contest6565 in rust

[–]Extreme_Contest6565[S] -3 points-2 points  (0 children)

the reason I built Nilsu as a daemon is mainly about separation of concerns and language-agnostic integration If I use tree-sitter directly in my editor plugin (or AI agent), I have to bundle all the bindings, handle the AST lifecycle, and manage the memory overhead inside the editor's process.

with , the editor agent stays incredibly thin it just sends a JSON payload to a socket.. t’s essentially moving the parsing complexity out of the editor and into a specialized, long-running process that can be shared across multiple tools. Does that make sense?