Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Looper refactor/redesign #25

Open
shuhaowu opened this issue Jan 9, 2023 · 0 comments
Open

Looper refactor/redesign #25

shuhaowu opened this issue Jan 9, 2023 · 0 comments

Comments

@shuhaowu
Copy link
Contributor

shuhaowu commented Jan 9, 2023

While writing the detailed documentation, I discovered a better way to write the looper based on a counter on the number of events that should have been executed. Thus, instead of documenting the algorithm as is, I documented the better algorithm, even tho the code doesn't actually implement this.

I believe this would be a better way to write the looper as opposed to the current design, which kind of works on the difference/deltas of the number of events that should have been executed. The reason it is better is that it would be easier to understand, easier to analyze, and possibly more correct for difficult-to-maintain rates. This rewrite should probably be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant