then et al support implicit conversion of objects to promises#2
Merged
then et al support implicit conversion of objects to promises#2
Conversation
future::Future support is built in
Member
Author
|
Might also be helpful for docs to point out that this is not how you take a result value and turn it into a promise (like |
Member
Author
|
Almost forgot, this PR also includes |
This file contains hidden or 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
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.
future::Future support is built in.
With this PR, you can seamlessly treat regular
future()results as promises.An unsolved problem is that contexts that can take either promises or non-promises (like Shiny render functions) would have no way to know whether to attempt converting something to a promise or not.