UInt2048

@lirbar Have you tried simply removing the angle_gl_backend library from whatever target you're building?

Right, that's correct. I assume it was more like a thousand days initially? It would take much longer to even out such a long gap. Tsurukame really should account for...

@rolfbjarne Wonder if it needs to be done sooner for the same reasons as #6213

@planetbeing Thanks so much for merging #15. The fix works so you should be able to close this issue!

@charlesaroutiounian The developer is not interested in PRs for major features due to the maintenance burden. Source: https://github.com/davidsansome/tsurukame/pull/524#issuecomment-1003937776

Review batch size is different than lesson batch size. Review batch size is an invisible selection pool you can’t see in the app, which has the effect of making meaning...

To elaborate, this is another consequence of batch size. When back-to-back reviews are disabled, batch size determines the number of reviews you need to wrap up — so if your...

@Arzorth Thanks for doing your diligence to find this issue instead of making a new one! I think implementing your request is a bit trickier than you might think. For...

@Arzorth In that case, the solution I proposed would be sufficient: you could in fact just store the maximum allowed amount decreasing it by one after each completed review and...

@nstaff Please ensure you have updated Tsurukame to the latest version, 1.29.