My previous posts showed mirror_bridge generating bindings and outrunning JIT compilers. This one is about what happens when things go wrong, because the quality of a binding library is also measured by how much it helps you when things don’t go as expected.

“I Love to Specialize Hash Functions for My C++ Classes” (No One, Ever)

We know Mirror Bridge generated bindings beat the standard Python interpreter. But how do they fare against the big guns?

You have a Python codebase. Thousands of lines. It works. Your team knows it. Your tests cover it. Your CI/CD deploys it.

JSON (JavaScript Object Notation) is a popular format for storing and transmitting data. It uses human-readable text to represent structured data in the form of attribute–value pairs and arrays. E.g., {"age":5, "name":"Daniel", toys:["wooden dog", "little car"]}. Ingesting and producing JSON documents can be a performance bottleneck.

TLDR

• Implemented a complex expected linear time algorithm for finding Minimum Spanning Tree.
• Found a bug in an implementation in a 13 years old paper.
• Code available at github