add Send restriction to resource table #15
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.
Hello I am back with more Send confusion :p
When calling async functions from the host using
.call_myfn(store).await
, it is required that the store's data isSend
. Keeping aResourceTable
inside of the store's data seems like the most common use case for it, so I changed thedyn Any
todyn Any + Send
to allow this.Looking at the tests it seems this was missed, as the tests with
ResourceTable
use a synchronous.call
, not async.