Deprecated setEx, instead by start(cb, ex) #400
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ChuanqiXu9
reviewed
Nov 5, 2024
ChuanqiXu9
reviewed
Nov 7, 2024
poor-circle
force-pushed
the
deprecated-setEx
branch
from
99c4af6 to
bd9f241
Compare
|
resolved |
ChuanqiXu9
approved these changes
Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
deprecated
Lazy::setEx()instead by Lazy::start(cb,ex), which is may not expected behavior.What is changing
Lazy::setEx()Lazy::start(cb,ex), which will start a coroutine and binding it to a new executor without scheduling immediately.Example