popzxc

6 ms·

1.
Omarchy on Mac(github.com)
2 points by popzxc 5h ago|0 comments
2.
Why building a Rust LSP is hard(rust-glancer.github.io)
1 points by popzxc 8h ago|0 comments
3.
Show HN: Rust Glancer 0.2 – new Rust LSP server targeting <100mb idle RSS(rust-glancer.github.io)
1 points by popzxc 15d ago|0 comments
4.
by popzxc 25d ago
And regarding salsa+rocksdb, actually Alex Kladov advocated exactly for that in the post about Rust Glancer and rust-analyzer architecture: https://matklad.github.io/2026/08/21/rust-glancer.html Though I beli
5.
by popzxc 25d ago
Well, it's hard to give a concise overview, but in short -- I use `wincode` for serde (without zero-copy deserialization though; I've tried zero-copy first with rkyv but it was not trivial at all so I abandoned this idea, plus FS
6.
by popzxc 25d ago
The exact shape is TBD (I target proc macros support for 0.3.0, whereas 0.2.0 will be about completeness/editors support), but in short -- I'm thinking about "plugin"/DSL architecture where proc macro _effects_ can
7.
by popzxc 25d ago
On the first question -- auto imports is an example of a "heavy" functionality since we indeed need to scan more than is imported in the project, which is why I'm still working on this to optimize properly (it's decently
8.
by popzxc 25d ago
Yup. Basically, I have been combining both a manager and IC role for years now, which certainly helps working with LLMs: I can "delegate", and I know when to "intervene". It certainly is a skill, but the issue with LLMs
9.
by popzxc 25d ago
> So you would essentially fully index only once per project, + whenever you upgrade dependencies or upgrade rustc? This is when you do full reindexing. > Is that only an incremental indexing with normally low RAM usage? Yup, on save
10.
by popzxc 25d ago
Exactly. You pay higher RAM usage price once, for 5-30 seconds at the very beginning of the project (or if you make changes that invalidate the dependency graph, which is rather rare). In 95% of cases and 99.999% of idle time using the edit
11.
by popzxc 25d ago
I would say that LLMs have really good understanding of LSPs, but they are not necessarily good at building them. Had I blindly followed the proposed flow, Rust Glancer wouldn't have reached a stage where it is at least remotely usable
12.
by popzxc 25d ago
Storing structures mmapp'd is actually very tricky. I have experimented with rkyv initially having this idea in mind, but gave up because the machinery just to power the archive types was causing complexity to explode. The thing with z
13.
by popzxc 26d ago
I will work on creating a more or less fair benchmark soon-ish, but right now the initial indexing typically consumes more RAM than rust analyzer does, but not awfully so. The difference, however, is that with Rust Glancer you don’t need fu
14.
by popzxc 26d ago
Coming in the next release (as well as nvim)!
15.
by popzxc 26d ago
I’m not sure if RA intentionally uses storage space itself. It can use storage when running build scripts/expanding proc macros, or when running flycheck diagnostics. In both cases, it’s because it runs cargo and it writes artifacts to
16.
by popzxc 26d ago
It's explained in the blog post, but in short: rust-analyzer stores the data it needs in memory all the time, while Rust Glancer might consume more memory during indexing (because it's not lazy and does more indexing), but after t
17.
by popzxc 26d ago
Well, most of stuff is not really ambiguous: if you have a struct and found its inherent impl for it, then methods from this impl block are related to this structure. If `a` has type `Foo` and then you have `let b = a;`, then `b` has type `
18.
by popzxc 26d ago
Thanks for the coverage and kind words! The title of the post is a bit more ambitious than what I am confident to guarantee, but I'll try my best to live up to it ^_^" Some comments on the thoughts post > I think that part can
19.
by popzxc 26d ago
In a way. It uses a different architecture, so it's not exactly "RA with something", but the main idea is similar: everything is on the disk, stuff is loaded only when it's needed.
20.
by popzxc 26d ago
Hey! Author here. Happy to answer any questions.
21.
Show HN: Messages: A runtime-agnostic actor library inspired by actix(github.com)
4 points by popzxc 5y ago|1 comments