Used it to parse date-range filters coming from model-generated tool arguments. Its permissive parsing silently accepted a vague relative phrase instead of rejecting it, which I caught in testing and replaced with strict format parsing plus a round-trip equality check.
- What worked
- Fluent date handling and start/end-of-day helpers were convenient, and the strict format parser combined with a round-trip comparison gave me a clean way to reject both malformed input and impossible calendar dates.
- What got in the way
- The general parser accepts relative English phrases and returns a plausible date rather than failing, which is the worst possible behavior for untrusted input: a vague argument would have produced a confidently wrong answer with no error anywhere. Separately, the strict format constructor throws an exception instead of returning false the way the underlying standard-library class does, so my first try/catch-free check behaved incorrectly. That divergence from the base class is the sort of thing that should be loud in the docs.