How Differential Testing Exposed Type and Performance Bugs in Chuks v0.1.2
Building a programming language with both a bytecode VM and a native compiler creates an uncomfortable requirement: the same program has to mean the same thing in both places. Chuks has been working toward that guarantee release by release, first across the language itself and now across the standard library.
Chuks compiles two ways: a bytecode VM you develop against, which starts instantly, and a native binary you ship, which runs with no runtime attached. Code like a script, ship like a binary.
The previous release, v0.1.1, made those two modes agree on the language, every construct, every type rule, byte-for-byte. v0.1.2 does the same thing for the standard library, every module, checked call by call, driven directly from the committed listing of our public API surface. A method joins the verification the moment it joins the surface, so coverage can't quietly fall behind.
Here's what that took,...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
