Thanks for reading. What outputs are you transforming? rustdoc JSON? Doxygen XML?

score 1 · canonical

Beautiful results

Thank you (and thanks for reading)

gave up on consistent theming

IME consistent fonts go a long way. CSS vars make it much more manageable now, too

If I’m looking at the rust docs, getting results for C/C++ would feel distracting

I’ve gone back and forth on this. My operating theory is that the top-level search UX should be consistent across the site, no matter what page you’re on. Note that the rustdoc search is still available when you’re on rustdoc pages. So there’s 2 search boxes on rustdoc pages. Which is potentially way more confusing. Not sure what the right move is here. After 6 months I’ll have more opinions

Is there a way to show just the rust docs if I’ve drilled down to that language?

I think you’d have to manually filter by URL, but yes, should be totally feasible via Pagefind search API: https://pagefind.app/docs/api/

I will update the post to discuss CSS stuff in more detail this week, that was another thing I meant to cover but didn’t have time for

score 1 · canonical

As you would hope (or expect) from JetBrains people, there’s actually quite a lot of interesting detail about how exactly they use embeddings for code search. Namely:

• Sometimes quantization but never (?) Matryoshka
• For a “suggested related code” feature they needed to preserve more precision
• Binary quantization!
• They use their fancy AST tools to determine chunks

score 2 · canonical

More explanation in this vid: https://youtu.be/VI3XekUlVmo

For Lobsters community what’s relevant is that he hacked this electronic instrument himself and represents some creative thinking about HCI.

score 1 · canonical