Let the generators state both directions
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
Let each synthetic generator that writes a closed either-or vary it across its
rows: the forward rate agreement generator writes Long unconditionally today.
2. Why
The forward rate agreement's mapper ignored the direction its document stated for as long as the family existed, and every witness agreed with the constant: the ORE example corpus states Long, and so does the generator. No test, dataset or screenshot could have shown the difference, which is why the defect survived review after review.
A fixture that varies a closed set is cheap, and it is the only witness that can fail. The same habit probably reaches the other either-ors the generators write — an option's long or short, a leg's payer, a call or a put. Count them before changing one, so the change lands as a rule rather than as one generator's patch.
3. References
- Carry the rates family's fields across the ORE boundary — the unit whose verifier found this.
fra_instrument_generator.cpp, the constant.