It appears as if, dates with numeral Decembers are not parsable by this library. (e.g. 2023-12-25, 12/24/23, etc.)
After a short investigation, I found a typo in the GRAMMAR.

This rule[sic] is not including the 12th month in the range.

        n_month => [
                (1..12)
                    .into_iter()
                    .flat_map(|i| vec![format!("{:02}", i), format!("{}", i)])
                    .collect::<Vec<_>>()
            ]

On my system, the first call to parse allocates 1.7 GiB of memory (and caused an OOM in my original use case). Tracing the allocations back, it appears that pidgin::matching::Matcher::parse is causing multiple ~500 MiB allocations in regex_automata.

Is this expected behavior? (If so, it should be documented, since it makes this library impossible to use in many applications.)

• <period> before/after/around <time>
• ordinal expressions for days of the month
• <n> <periods> ago/from now
• <year>
• "the fifteenth", "the 1st of March", "5-6"
• noon, midnight
• Friday the 13th

add expression

Hi!

I've used this library for a Matrix bot to set reminders. We currently type "18:00 today", because "18:00" is in the past (it assumes yesterday). Is it possible to somehow add a field to Config, to configure two_timer to assume times lie in the future, instead of in the past?

Thanks!

Ruben