广场

Enabling the parallel frontend on nightly

TL;DR: We are enabling the parallel frontend of the Rust compiler on nightly by default, to find remaining issues in preparation for its stabilization. Context The Rust compiler has been using multiple threads to compile code in its "backend" part (using LLVM) for a long time. However, its "frontend" part (which includes type checking and borrow checking) has been executing sequentially, on a single thread, which of course limits the performance of the compiler. If you are interested in a more in-depth explanation of parallelism in the Rust compiler, see this previous post . The compiler frontend actually had support for running in parallel for a long time, but it was not enabled by default …

Rust Blog开发技术英文

Introducing MathHelm: A Place to discuss AI-generated papers

[This is a guest post by the MathHelm scientific committee, whose membership is listed at the bottom of this post. -T.] Mathematics depends on our regular conversations with colleagues and with the wider public. They help us share ideas, deepen our collective understanding, see where the field stands, and decide what to explore next. They […]

What's new其他英文

Fine-Grained RAG Permissions with Qdrant and SpiceDB

Fine-Grained RAG Permissions with Qdrant and SpiceDB Time: 45 min Level: Intermediate Output: GitHub A standard RAG pipeline answers questions using information retrieved from your documents. Qdrant stores their embeddings and associated metadata and finds relevant documents to provide as context to the language model. But without an authorization step, any user can get an answer from any document in the collection, including documents they aren’t allowed to read. The OWASP Top 10 for LLM Applications lists this kind of leak as Sensitive Information Disclosure.

QdrantAI 工具英文

Restructuring changkun.de

Since the “architecture upgrade” at the end of 2020, I have rarely touched the overall structure of changkun.de . At the end of The All in Go Stack , I expressed the hope that the new “organisational architecture”, backed by Go’s compatibility, would serve reliably for more than three years. Looking back now, it served for almost six years, and for most of that time it indeed had no major problems. But over those six years, more and more things accumulated on the server: whenever I needed a new feature, I would add a service, a route or a GitHub Action, and never come back to tidy up afterwards. Little by little, the website drifted back into an “organisationally chaotic” state. This weekend…