Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

AI-Assisted SQLite parse_number() Extensions Benchmarked in C and Rust

AI summary

Simon Willison’s Weblog describes an AI-assisted comparison of four SQLite extensions implementing the same parse_number() behavior in C and Rust. The optimized C version ran at 16–19 ns per row, roughly twice as fast as the Rust versions, while all four implementations produced matching results across eight million fuzz checks. The initial Rust binaries were also much larger than the C extension.

In-depth insight

The experiment provides a concrete engineering comparison of implementation size, parsing performance and correctness for a practical SQLite extension, showing how a compact C fast path can close or reverse a Rust performance advantage.

Research: parse_number() as a SQLite extension: C vs Rust

Simon Willison’s Weblog

Newsletter

Sponsored by: Dynatrace — Your coding agent can read your code but can’t see how it runs in production. Read the blog to see how Dynatrace MCP closes that gap.

8th November 2026

Research parse_number() as a SQLite extension: C vs Rust — Four SQLite extensions implement the same `parse_number()` behavior in C and Rust, with tests covering type preservation, parsing rules, and floating-point accuracy. The optimized C implementation was fastest at 16–19 ns per row, about twice as fast as the Rust versions and far faster than SQL `replace()`. Plain C was slower on decimals because it relied on `strtod()`, while a compact fast path closed that gap; all versions matched across 8 million fuzz checks.

#SQLite#C#Rust

Original · 2 min readRead the original
Group chat

No comments yet. Start the conversation.