miniblog.

← Back to all posts
Jan 6, 2022 at 17:51
Interesting people keep popping up on the difftastic issue tracker. Here's a discussion of applying structural diff techniques to language-aware merging:
Textual diffing can be very slow · Issue #86 · Wilfred/difftastic
Textual diffing can be very slow · Issue #86 · Wilfred/difftastic
See e.g. magit.info-1 in Wilfred/.emacs.d@0bb2a28

Related Posts

Mar 8, 2026 at 22:03
7
Anthropic used Claude to write a C compiler in Rust (CCC). I've really enjoyed following the discussion. The initial post shows how they wrote the harness with GCC as an oracle and a prompt specifying a design using SSA. The author has clear domain expertise. https://www.anthropic.com/engineering/building-c-compiler
Jan 23, 2026 at 00:09
1
Futhark's design is deliberately trying to stay simple to keep long term design sustainable. The author also has an interesting discussion of relative versus absolute paths in import syntax, and how relative paths can make local analysis easier.
Designing a Programming Language for the Desert
A high-performance and high-level purely functional data-parallel array programming language that can execute on the GPU and CPU.
Jul 29, 2023 at 17:33
Go has a wonderful, accessible discussion of how it does inlining today, the downsides, and the plans for 1.22:
Go 1.22 inlining overhaul
Go 1.22 inlining overhaul
Go 1.22 inlining overhaul , with contributions from , , , and Last update: The Go compiler’s inliner has never been particularly good. It wasn’t until Go 1.12, released in 2019, that the Go compiler supported inlining more than leaf functions, and we’ve slowly chipped away at more limita...