| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There’s no point in having an opaque user data pointer when we’re already using `std::function`.
Split `Stop(true)` and `Stop(false)` into separate methods since the actions performed by these are fully distinct.
|
@jasnell So it turned out there is a reason why the cleanup hook is on the TimerWrapHandle class – it’s because otherwise, the TimerWrapHandle doesn’t know whether the cleanup hook has been called or not, and will then try to call Close again once it’s being destroyed, possibly using a TimerWrap object that doesn’t exist anymore. So I’ve reverted that bit. :) |
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/32265/ (:green_heart:) |
Sorry, something went wrong.
There’s no point in having an opaque user data pointer when we’re already using `std::function`. PR-URL: #34252 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com> Reviewed-By: David Carlier <devnexen@gmail.com>
Split `Stop(true)` and `Stop(false)` into separate methods since the actions performed by these are fully distinct. PR-URL: #34252 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com> Reviewed-By: David Carlier <devnexen@gmail.com>
|
This does not land cleanly on v14.x, should this be backported? |
Sorry, something went wrong.
There’s no point in having an opaque user data pointer when we’re already using `std::function`. PR-URL: #34252 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com> Reviewed-By: David Carlier <devnexen@gmail.com>
Split `Stop(true)` and `Stop(false)` into separate methods since the actions performed by these are fully distinct. PR-URL: #34252 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com> Reviewed-By: David Carlier <devnexen@gmail.com>
There’s no point in having an opaque user data pointer when we’re already using `std::function`. PR-URL: #34252 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com> Reviewed-By: David Carlier <devnexen@gmail.com>
Split `Stop(true)` and `Stop(false)` into separate methods since the actions performed by these are fully distinct. PR-URL: #34252 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com> Reviewed-By: David Carlier <devnexen@gmail.com>
| Back | FazBrowse Home | New Git URL |
src: remove user_data from TimerWrap
There’s no point in having an opaque user data pointer when we’re
already using std::function.
src: refactor TimerWrap lifetime management
Move the cleanup hook into the TimerWrap, because it should
always be present when that class is being used, and split
Stop(true) and Stop(false) into separate methods since the
actions performed by these are fully distinct.
Checklist