XCM v6 #7123
Draft
XCM v6 #7123
+2,809
−874
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
|
This is much more complicated than I initially anticipated. The |
|
most of the Xcm v5 code are written without any consideration of future compatibility, and now someone have to refactor all of it... |
|
approach looks good! @xlc if you don't have the bandwidth to do this to completion (likely), I'm sure we can find someone in the ecosystem to do it, especially if you provide a good plan/framework/starting-point - let me know |
|
@acatangiu that will be great. I will spend a few more days to do the core refactoring and then someone can help fix integrations with different runtimes and remaining tests |
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.
closes #7095
Setup XCM v6 but with a more extensible approach. This should be 100% ABI with XCM v5 currently but need tests to assert that.
This is only a (not so) quick draft and looking for initial feedbacks.
Ideally, in future XCM versions, we only need to implement the new instructions without the need to duplicate all the existing ones.
TODOs: