https://www.bvbej.com/tags/%E7%B3%BB%E7%BB%9F%E7%BC%96%E7%A8%8B/Recent content in 系统编程 on BvBeJ的小站Hugozh-CNSat, 23 May 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-ffi-error-modeling/Sat, 23 May 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-ffi-error-modeling/错误码和上下文要分层表达，避免边界信息丢失https://www.bvbej.com/posts/rust-pin-unpin-explained/Wed, 20 May 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-pin-unpin-explained/理解 Pin 才能真正看懂 async/await 生成的状态机https://www.bvbej.com/posts/cpp-atomics-false-sharing/Tue, 12 May 2026 00:00:00 +0000https://www.bvbej.com/posts/cpp-atomics-false-sharing/cache line 争用常常比锁本身更先成为瓶颈https://www.bvbej.com/posts/rust-ffi-zero-copy-contract/Tue, 12 May 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-ffi-zero-copy-contract/跨语言零拷贝不是“传个指针”这么简单，契约不清就会踩 UB。https://www.bvbej.com/posts/rust-unsafe-audit-checklist/Thu, 07 May 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-unsafe-audit-checklist/unsafe 不可避免，但必须可审计、可证明、可回归https://www.bvbej.com/posts/cpp-coroutine-lifetime-pitfalls/Tue, 05 May 2026 00:00:00 +0000https://www.bvbej.com/posts/cpp-coroutine-lifetime-pitfalls/协程把控制流拆开后，对象生命周期边界更容易被误判https://www.bvbej.com/posts/rust-cpp-ffi-safe-boundary/Thu, 30 Apr 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-cpp-ffi-safe-boundary/跨语言调用最容易出问题的不是语法，而是生命周期和错误语义https://www.bvbej.com/posts/rust-zero-copy-serialization/Thu, 23 Apr 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-zero-copy-serialization/零拷贝并非银弹，但在高吞吐链路里常常是关键优化点https://www.bvbej.com/posts/cpp-cache-friendly-data-layout/Mon, 20 Apr 2026 00:00:00 +0000https://www.bvbej.com/posts/cpp-cache-friendly-data-layout/比起花哨技巧，数据布局通常是 C++ 性能的第一杠杆https://www.bvbej.com/posts/cpp-memory-pool-performance/Thu, 16 Apr 2026 00:00:00 +0000https://www.bvbej.com/posts/cpp-memory-pool-performance/当 new/delete 成为热点时，内存池往往比继续抠业务逻辑更有效https://www.bvbej.com/posts/rust-ownership-and-borrow/Wed, 08 Apr 2026 00:00:00 +0000https://www.bvbej.com/posts/rust-ownership-and-borrow/从 C++ 转 Rust，最难跨越的不是语法，而是思维