feat: derive Encode
and Subscribe
, not EncodeSync
#1690
Merged
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.
Feature or Problem
While
Encode
andSubscribe
traits do support async values, we do not currently support eitherstream<T>
,future<T>
orresource
types in WIT definitions we generate bindings for, therefore we can always assume that values we generate these implementations for do not have any asynchronous values embedded in them.Related Issues
Release Information
Consumer Impact
This allows binding generation for
option
,result
etc. types - everything is supported except for preview3 async and resources.Testing
Unit Test(s)
Acceptance or Integration
Manual Verification