<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Rust on BvBeJ的小站</title><link>https://www.bvbej.com/tags/rust/</link><description>Recent content in Rust on BvBeJ的小站</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.bvbej.com/tags/rust/feed.xml" rel="self" type="application/rss+xml"/><item><title>Rust 异步测试策略：稳定性与可重复性</title><link>https://www.bvbej.com/posts/rust-async-testing-strategy/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-async-testing-strategy/</guid><description>异步测试 flaky 的根因通常是时序假设写死</description></item><item><title>Rust FFI 错误模型：跨语言返回值语义设计</title><link>https://www.bvbej.com/posts/rust-ffi-error-modeling/</link><pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-ffi-error-modeling/</guid><description>错误码和上下文要分层表达，避免边界信息丢失</description></item><item><title>Rust Tokio Runtime 调优：任务调度与阻塞隔离</title><link>https://www.bvbej.com/posts/rust-tokio-runtime-tuning/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-tokio-runtime-tuning/</guid><description>Tokio 默认配置能跑，但高负载下需要主动治理阻塞与唤醒抖动。</description></item><item><title>Rust Pin/Unpin：异步底层模型快速理解</title><link>https://www.bvbej.com/posts/rust-pin-unpin-explained/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-pin-unpin-explained/</guid><description>理解 Pin 才能真正看懂 async/await 生成的状态机</description></item><item><title>Rust mmap 索引服务的一致性与崩溃恢复</title><link>https://www.bvbej.com/posts/rust-mmap-index-consistency/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-mmap-index-consistency/</guid><description>mmap 提升读性能，但元数据原子更新与 fsync 语义必须讲清楚。</description></item><item><title>Rust Channel 背压模式：有界队列与拒绝策略</title><link>https://www.bvbej.com/posts/rust-channel-backpressure-patterns/</link><pubDate>Sun, 17 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-channel-backpressure-patterns/</guid><description>高负载下的可预测行为，比单次吞吐更重要</description></item><item><title>Rust Serde 版本演进：兼容旧数据的实践</title><link>https://www.bvbej.com/posts/rust-serde-versioning-strategy/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-serde-versioning-strategy/</guid><description>协议演进要优先保证向后兼容，再考虑字段重构</description></item><item><title>Rust FFI 零拷贝接口契约：布局、生命周期与错误边界</title><link>https://www.bvbej.com/posts/rust-ffi-zero-copy-contract/</link><pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-ffi-zero-copy-contract/</guid><description>跨语言零拷贝不是“传个指针”这么简单，契约不清就会踩 UB。</description></item><item><title>Rust tracing 字段设计：日志可检索性的关键</title><link>https://www.bvbej.com/posts/rust-tracing-field-design/</link><pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-tracing-field-design/</guid><description>结构化日志的价值取决于字段规范而不是打印多少行</description></item><item><title>Rust 状态机建模：让服务流程可验证</title><link>https://www.bvbej.com/posts/rust-state-machine-services/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-state-machine-services/</guid><description>把业务流程写成显式状态机，能显著减少隐式分支 bug</description></item><item><title>Rust unsafe 审计清单：把风险控制在可解释范围</title><link>https://www.bvbej.com/posts/rust-unsafe-audit-checklist/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-unsafe-audit-checklist/</guid><description>unsafe 不可避免，但必须可审计、可证明、可回归</description></item><item><title>Rust Async 的 Cancellation Safety：避免半提交状态</title><link>https://www.bvbej.com/posts/rust-async-cancellation-safety/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-async-cancellation-safety/</guid><description>取消并不等于回滚，未设计的中断会留下难排查的数据破坏。</description></item><item><title>Rust async trait 性能取舍：泛型与动态分发</title><link>https://www.bvbej.com/posts/rust-async-trait-performance/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-async-trait-performance/</guid><description>抽象层做得越漂亮，越要关注是否引入了不必要的动态开销</description></item><item><title>Rust Tokio 取消安全：避免半完成状态</title><link>https://www.bvbej.com/posts/rust-tokio-cancellation-safety/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-tokio-cancellation-safety/</guid><description>异步任务可取消不等于安全可取消，关键是边界和幂等</description></item><item><title>Rust 与 C++ FFI：边界安全和所有权约定</title><link>https://www.bvbej.com/posts/rust-cpp-ffi-safe-boundary/</link><pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-cpp-ffi-safe-boundary/</guid><description>跨语言调用最容易出问题的不是语法，而是生命周期和错误语义</description></item><item><title>Rust 无锁结构中的内存回收：Epoch 与 Hazard Pointer 对比</title><link>https://www.bvbej.com/posts/rust-lockfree-memory-reclamation/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-lockfree-memory-reclamation/</guid><description>无锁算法真正难点不是 CAS，而是安全回收被并发读取的节点。</description></item><item><title>Rust Axum 中间件分层：认证、限流、追踪怎么排</title><link>https://www.bvbej.com/posts/rust-axum-middleware-layering/</link><pubDate>Mon, 27 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-axum-middleware-layering/</guid><description>中间件顺序会直接影响安全性和可观测性，分层要有明确意图</description></item><item><title>Rust 错误分层：把排障信息留在正确位置</title><link>https://www.bvbej.com/posts/rust-error-context-observability/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-error-context-observability/</guid><description>错误处理不只是返回 Result，更关键是分层定义和上下文补全</description></item><item><title>Rust 零拷贝序列化：什么时候值得做</title><link>https://www.bvbej.com/posts/rust-zero-copy-serialization/</link><pubDate>Thu, 23 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-zero-copy-serialization/</guid><description>零拷贝并非银弹，但在高吞吐链路里常常是关键优化点</description></item><item><title>Rust 与 C++ FFI 实战：先稳住边界再谈性能</title><link>https://www.bvbej.com/posts/rust-ffi-with-cpp-practice/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-ffi-with-cpp-practice/</guid><description>从 ABI、所有权到错误处理，整理一套可落地的 Rust/C++ 混编方案</description></item><item><title>Rust Tokio 背压控制：异步系统别只会拼命 spawn</title><link>https://www.bvbej.com/posts/rust-tokio-backpressure/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-tokio-backpressure/</guid><description>异步不等于无限并发，背压设计决定了 Tokio 服务在高负载下是稳定还是失控</description></item><item><title>Rust 异步数据库访问：连接池、超时与稳定性</title><link>https://www.bvbej.com/posts/rust-async-db-pool/</link><pubDate>Thu, 16 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-async-db-pool/</guid><description>异步访问数据库不只是把函数改成 async，更关键的是控制连接、等待时间和失败路径</description></item><item><title>Rust Tokio 优雅停机：让服务真正可控</title><link>https://www.bvbej.com/posts/rust-tokio-graceful-shutdown/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-tokio-graceful-shutdown/</guid><description>聊聊 Tokio 服务里的信号处理、任务取消与优雅退出</description></item><item><title>写给 C++ 程序员的 Rust 入门指南</title><link>https://www.bvbej.com/posts/rust-for-cpp-programmers/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-for-cpp-programmers/</guid><description>用你熟悉的 C++ 概念对照学习 Rust，事半功倍</description></item><item><title>Rust 错误处理：从 panic 到 anyhow</title><link>https://www.bvbej.com/posts/rust-error-handling-practical/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-error-handling-practical/</guid><description>Rust 的错误处理比 C++ 优雅太多了</description></item><item><title>Rust 所有权与借用：我的理解之路</title><link>https://www.bvbej.com/posts/rust-ownership-and-borrow/</link><pubDate>Wed, 08 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.bvbej.com/posts/rust-ownership-and-borrow/</guid><description>从 C++ 转 Rust，最难跨越的不是语法，而是思维</description></item></channel></rss>