XCM V5 - SetHints instruction #6566
Conversation
|
/cmd fmt |
|
Command "fmt" has started 🚀 See logs here |
|
Command "fmt" has finished ✅ See logs here |
|
/cmd fmt |
|
Command "fmt" has started 🚀 See logs here |
|
Command "fmt" has finished ✅ See logs here |
|
/cmd fmt |
|
Command "fmt" has started 🚀 See logs here |
|
Command "fmt" has finished ✅ See logs here |
polkadot/xcm/procedural/tests/ui/builder_pattern/unexpected_attribute.stderr
Outdated
Show resolved
Hide resolved
| - audience: Runtime Dev | ||
| description: | | ||
| The new SetHints instruction is a repackaging of SetAssetClaimer that also allows future | ||
| "hints" which alter the default behaviour of the executor. |
There was a problem hiding this comment.
What are the "hints" and what's the motivation behind it? I am missing the full context of this PR...
Is there an RFC or some documentation for that?
There was a problem hiding this comment.
RFC 107, I've added it to the prdoc
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
|
/cmd fmt |
|
Command "fmt" has started 🚀 See logs here |
|
Command "fmt" has finished ✅ See logs here |
Last feature we wanted for V5, changing `SetAssetClaimer` to be just one of many possible "hints" that you can specify at the beginning of your program to change its behaviour. This makes it easier to add new hints in the future and have barriers accept them. --------- Co-authored-by: GitHub Action <action@github.com>
Backporting #6566 to stable2412 Last feature we wanted for V5, changing `SetAssetClaimer` to be just one of many possible "hints" that you can specify at the beginning of your program to change its behaviour. This makes it easier to add new hints in the future and have barriers accept them. --------- Co-authored-by: GitHub Action <action@github.com>
Last feature we wanted for V5, changing `SetAssetClaimer` to be just one of many possible "hints" that you can specify at the beginning of your program to change its behaviour. This makes it easier to add new hints in the future and have barriers accept them. --------- Co-authored-by: GitHub Action <action@github.com>
Last feature we wanted for V5, changing
SetAssetClaimerto be just one of many possible "hints" that you can specify at the beginning of your program to change its behaviour.This makes it easier to add new hints in the future and have barriers accept them.