miniblog.

← Back to all posts
Jan 29, 2017 at 17:06
TIL that making an ABI mistake can cause segfaults in Rust, without unsafe or warnings!
tuple structs cause FFI segfaults on 32-bit Linux · Issue #39394 · rust-lang/rust
tuple structs cause FFI segfaults on 32-bit Linux · Issue #39394 · rust-lang/rust
Given the following Rust code, compiled as a staticlib: extern crate libc; #[repr(C)] pub struct LispObject(libc::c_int); #[no_mangle] pub extern "C" fn fcdr(list: LispObject) -> LispObject { print...

Related Posts

Sep 11, 2026 at 22:08
3
I've been experimenting with LLM autoresearch. I prompted Sol to make difftastic faster without changing output on the test suite, and log everything it tried: https://github.com/Wilfred/difftastic/blob/c6e9c6fed4c71276a8b0e377c92695c3d929dc7f/PERF_RESEARCH_LOG.md It found some interesting performance tweaks, although it's too tolerant of complexity.
difftastic/PERF_RESEARCH_LOG.md at c6e9c6fed4c71276a8b0e377c92695c3d929dc7f · Wilfred/difftastic
difftastic/PERF_RESEARCH_LOG.md at c6e9c6fed4c71276a8b0e377c92695c3d929dc7f · Wilfred/difftastic
a structural diff that understands syntax 🟥🟩. Contribute to Wilfred/difftastic development by creating an account on GitHub.
Aug 28, 2026 at 20:47
2
Bevy has an amazing approach to code review that requires two reviews by the community before a maintainer will review and merge. "We let anyone submit PRs without vetting: why is the bar higher for reviewing?" https://shaping.systems/blog/open-code-review/
Aug 24, 2026 at 23:32
The literal 0xffu8 in Rust is pretty tricky to read without syntax highlighting. It looks like a plain hexadecimal value at first. (Why not have syntax highlighting? Ironically I was debugging and improving VS Code's Rust highlighting.)