Component model prepwork & RSocket alignment #449
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
jsoverson
force-pushed
the
rsocket-alignment
branch
from
bae4946
to
614e101
Compare
fawadasaurus
approved these changes
Oct 12, 2023
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.
This PR updates to the latest wasmRS which brings in some re-alignment with RSocket and changes necessary to support component-model wasm components.
wickwill remain backward-compatible with existing components, but new components will not run on olderwickversions. This is not uncommon but is worth noting.Other changes:
stdlib(wick::namespace). It was never documented, only used in tests, and most operations were superseded bycore::or external components.command-type modules.unary_with_outputsandgeneric_rawoperation types to simplify common op definitions.