Revisiting poro_validator: the code, the argument, and the benchmark
I revisited a Ruby validator I wrote years ago, with AI assistance, containers, and fresh benchmarks. Some ideas held up. The code and the performance argument needed a closer look.