-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Remove one kind of Timer #8488
Remove one kind of Timer #8488
Conversation
If the consensus is that the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I see some pros of the Callback-based timers (they allow to statically allocate memory for the callback and hence guarantee that some critical operations will be executed), I've never understood why the code for processing them is so different than the timers allocated from the common pool, and the Callback
class seems too heavy for the job. Thus I support the change 👍
#### Problem System::Layer has two functionally equivalent kinds of timer, which is a maintenance burden. One of them is very little used, and not currently supported on all platforms. #### Change overview Remove the kind of timer that takes a `Callback<>`. #### Testing Revised the unit test. The changed calls are both in ESP32, which is tested in CI using QEMU.
f0a4014
to
a5f7a0a
Compare
Size increase report for "esp32-example-build" from 32c1393
Full report output
|
Size increase report for "nrfconnect-example-build" from 32c1393
Full report output
|
Size increase report for "gn_qpg-example-build" from 32c1393
Full report output
|
* Remove one kind of Timer #### Problem System::Layer has two functionally equivalent kinds of timer, which is a maintenance burden. One of them is very little used, and not currently supported on all platforms. #### Change overview Remove the kind of timer that takes a `Callback<>`. #### Testing Revised the unit test. The changed calls are both in ESP32, which is tested in CI using QEMU. * review
Problem
System::Layer
has two functionally equivalent kinds of timer,which is a maintenance burden. One of them is very little
used, and not currently supported on all platforms.
Change overview
Remove the kind of timer that takes a
Callback<>
.Testing
Revised the unit test. The changed calls are both in ESP32,
which is tested in CI using QEMU.