-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
timers: allow passing delay to timer.refresh() #40434
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
base: main
Are you sure you want to change the base?
Conversation
This comment has been minimized.
This comment has been minimized.
7ddac5c to
10d58e7
Compare
This comment has been minimized.
This comment has been minimized.
10d58e7 to
18ddfd5
Compare
This comment has been minimized.
This comment has been minimized.
18ddfd5 to
b959c50
Compare
This comment has been minimized.
This comment has been minimized.
|
@nodejs/timers |
b959c50 to
29f5a66
Compare
|
@mscdex ... can I ask you to provide a short change description and rationale? |
benjamingr
left a comment
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.
I'd like to know why/for what this is useful before this is merged?
Like - I know there is probably a reasonable use case for this but I don't know what it is
|
@benjamingr In my particular case I have a queue of waiting tasks, each with varying start timestamps. With the changes in this PR I can reuse a single timer object for the entire queue and simply do something like |
a4510d4 to
efff092
Compare
efff092 to
1ae03a2
Compare
1ae03a2 to
4ed6584
Compare
|
@jasnell I'm not sure what you're asking for. Were you just interested in hearing a use case like @benjamingr ? |
|
This needs a rebase |
No description provided.