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

ZTimer clocks: Consider moving to ZST #21

Open
chrysn opened this issue Oct 3, 2022 · 1 comment
Open

ZTimer clocks: Consider moving to ZST #21

chrysn opened this issue Oct 3, 2022 · 1 comment

Comments

@chrysn
Copy link
Member

chrysn commented Oct 3, 2022

ZTimer clocks are currently word-sized, but mutually incompatible because they carry their rate is part of the type anyway. Given that it's highly unlikely that clock using code would be monomorphized on different clocks of the same rate, it might be a good idea to move the clock into something that just has type-level information about the clock.

This would probably change the clock types as they'd gain a new parameter (and there could be a default to make that compatible, but it would be different across the three RIOT provided clocks).

@chrysn
Copy link
Member Author

chrysn commented Oct 3, 2022

This would help with #9, as there could then be a Default implementation.

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