Integrations of Load balance & Easy days

[L-M-Sherlock]

These two features require Anki to maintain a record of how many cards are due on each day.

As an initial idea, we may maintain this record in StateContext.

[dae]

Yep - my initial thought is we could store the counts per day there, and adjust the counts each time a card is answered.

One thing to think about is the long tail - large/old collections could potentially have thousands or tens of thousands of different due dates. What if we limited the features to a shorter time span, such as cards due in the next 3 months? For things like load balancing, it's probably not so useful to be balancing cards when they're so far out anyway, and as they become closer, younger cards would still be load balanced on those days. WDYT?

[L-M-Sherlock]

What if we limited the features to a shorter time span, such as cards due in the next 3 months?

It's totally acceptable. And we can also skip load balancing if the next due date is pretty far.

[Expertium]

An important question: when will Load Balancing be applied? After each review is probably too computationally expensive, although I may be underestimating Rust. So I'm guessing when the user clicks "Sync"?

[dae]

If we have a cached dictionary of daily due numbers, balancing can happen as cards are answered.