Ferrilab
This is where I write about the experience of creating the Ferrilab project.
Documentation for Ferrilab crates is primarily found in their API documentation, internal code comments, or the associated reference manual. However, there are some parts of the experience of developing these projects that don’t fit in the technical documentation, but are still worth writing down. That writing lives here.
These generally take the form of more pedagogical or exploratory texts rather than engineering documents, and try to be written to an audience that is interested in or aware of Ferrilab as a concept, but are not necessarily actively working with it as a dependency or on it as a direct project.
Articles
-
Introducing Ferrilab
()
I finally came up with a name I liked for the greater
bitvec
project collection, and several months later, a logo that I don’t hate. Here they are! -
No User Serviceable Parts Inside
()
I’m having troubles with Miri (again) and this is a snapshot of my understanding of the problem at time of writing.
-
Version One
()
I have finally completed
bitvec
. -
Runtime Alias Detection
()
My
bitvec
project is composed of a very small handful of core engineering components without which the project fundamentally cannot exist. This article addresses the most theoretically important: pointer-value alias analysis. -
The Ad-Dressing of Bits
()
My
bitvec
project is composed of a very small handful of core engineering components without which the project fundamentally cannot exist. This article addresses the pointer encoding allowing it to interact with the language core libraries. -
Polyglot Projects
()
An exploration of how I wrote a C++ binding API for my Rust library.