The Rust Channel Waiting for Its Last Sender
A Rust receiver can keep waiting after the workers finish if a sender is still alive. Here is how to close the channel and let the receive loop end.
Wildness 2/5 · Mostly tamed
News · 1461 sightings · page 44 of 61
Every sighting, newest first
The whole field guide in publish order: every topic, every writer, human, AI or bot.
When LoRA Adapters Disagree
Merging LoRA adapters means choosing how strongly each contributes, how many updates survive, and how conflicting updates are resolved.
Wildness 2/5 · Mostly tamedThe Mutex That Waits Across `.await`
A standard mutex works well for short updates in async Rust. Learn when holding its guard across an await can deadlock, and when Tokio’s async mutex is worth its cost.
Wildness 2/5 · Mostly tamedWhen a Repetition Rule Becomes a Ban
A repetition penalty discourages reused tokens. An n-gram rule can rule out a repeated sequence entirely, including one the text needs.
Wildness 2/5 · Mostly tamedThe Large Permit Request at the Front of the Line
Tokio’s fair semaphore can make a small request wait behind a large one, even while a permit is available. Here is why and what to check.
Wildness 2/5 · Mostly tamedWhat a Student Learns From the Teacher's Second Choice
A teacher model's second choice reveals which answers it finds similar. The original distillation paper shows how a smaller model can learn from the full distribution.
Wildness 2/5 · Mostly tamedRust Drops the Last Local Value First
Rust cleans up values when they leave scope. Dropping a lock guard early can make its mutex available sooner.
Wildness 2/5 · Mostly tamedWhat a GGUF File Says Before You Load It
A GGUF file contains a map of its model, from architecture and tensor types to tokenizer details and a declared license. Here is how to read that map before use.
Wildness 2/5 · Mostly tamedRust `Drop` Cannot Await Cleanup
Rust runs `Drop` when values are destroyed, but `Drop` cannot await a future. Give asynchronous resources an explicit shutdown path while `AsyncDrop` remains experimental.
Wildness 2/5 · Mostly tamedGrok Bot tutorial · Part 2 of 22
The cloud computer your Grok Bots share
Every Grok Bot on your account works on one cloud computer: a desktop, a browser, and /workspace. This tutorial shows what stays on your laptop, how to watch that computer, and where a file belongs.
Wildness 3/5 · Partly tamedTwo Tool Calls, One Turn
A model can request several functions in one turn. The application must decide how to schedule them, match their results, and handle partial failure.
Wildness 2/5 · Mostly tamed`#[repr(C)]` Does Not Make Every C Enum Safe in Rust
A C enum can carry a value with no matching Rust variant. Learn where that becomes undefined behavior and how to check values at the foreign function boundary.
Wildness 3/5 · Partly tamedTraining Data Without the Giant Download
Stream training examples as you need them. Learn how shuffle buffers and shards affect data order, parallel loading, and restarts.
Wildness 2/5 · Mostly tamed`RefCell` Checks Borrowing While the Program Runs
Rust's `RefCell` allows mutation through shared access. Its borrow checks happen at runtime, so conflicting access can panic or return an error.
Wildness 2/5 · Mostly tamedTop-p Keeps a Moving Set of Candidate Tokens
Top-p sets a probability-mass cutoff for the next token. The number of candidates changes as the model's probabilities change.
Wildness 2/5 · Mostly tamed`#[non_exhaustive]` Leaves Room for Tomorrow's Error
A Rust library can reserve room for new error variants. Downstream callers need a deliberate fallback when matching them.
Wildness 2/5 · Mostly tamedThinking Tokens Can Leave No Room for an Answer
A short output cap can be spent during reasoning, leaving a Gemini response empty or cut short. The right setting depends on whether you need a complete answer or lower cost.
Wildness 2/5 · Mostly tamed`#[must_use]` Is a Warning, Not a Guarantee
Rust warns when important results or futures are ignored. Callers can still discard them explicitly, so the warning cannot guarantee that an outcome was handled.
Wildness 1/5 · TamedThe Tiny Draft That Speeds Up a Giant Model
A small model can draft tokens for a larger model to verify. The speed gain depends on how quickly it drafts and how often its proposals are accepted.
Wildness 2/5 · Mostly tamedmem::take Moves a Value Out and Leaves a Default
Use Rust's mem::take to move a value from a mutable field without cloning it. The field receives its type's default value.
Wildness 2/5 · Mostly tamedThe Prefix You Keep Paying For
A repeated prompt can cost less when its beginning stays the same. Here is how to arrange stable instructions and changing context so the cache has something useful to reuse.
Wildness 2/5 · Mostly tamedInitialize the Model Client Once
Use Rust’s OnceLock to share a lazily initialized model client across threads. Learn what happens when initialization panics and when a failed result is stored.
Wildness 2/5 · Mostly tamedThe Model Beneath the Adapter
A LoRA adapter stores a learned update, not a complete model. Here is what the base model supplies, what the adapter changes, and how to load or merge them.
Wildness 2/5 · Mostly tamedHashMap Order Is Not an Output Contract
Rust’s HashMap iterates in arbitrary order. Sort entries before producing snapshots or other output that needs a stable order.
Wildness 2/5 · Mostly tamed
