01 Apr 2022
Hello friends. This is another bucket-of-updates kind of newsletter.
I’m hoping to write some more in-depth content soon (things like using CrossHair in practice, what CrossHair v1.0 looks like, a comparison with fuzzing). Let me know what you want to hear about too!
Since v0.0.20, CrossHair has complete string support! CrossHair can reason about every single string method and every single regular expression feature (albeit with varying effectiveness).
Be sure to let me know how it goes if you try it out.
SemVer is frequently criticized on the basis that every code change has the potential to break someone. We are then challenged to describe what “backwards-compatible” really means.
What if we used contracts to define “backwards-compatible?”
I’ve proposed a variant of SemVer, Contractual SemVer, to explore that idea.
CrossHair can help library authors and consumers using Contractual SemVer, too. See this example.
At present, CrossHair is “bug finder” and not a verification tool: in particular, your code can easily have bugs that CrossHair does not discover. See this discussion for details.
However, Loïc Montandon is actively pushing CrossHair in the verification-tool direction. As a result of his work, CrossHair will:
I am really exicted about this work. Stay tuned for the details.