Conversation
Improves use of managed `Chain<...>` in cases where chain elements may not be known at compile time apart from a prefix set
Member
|
Thanks, I'm happy with this proposal to go to the Working Group. I'll see about scheduling a meeting soon. |
Member
|
Approved, no objections whatsoever (huzzah!) |
Perksey
approved these changes
Jan 7, 2023
auto-merge was automatically disabled
January 7, 2023 23:29
Head branch was pushed to by a user without write access
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary of the PR
Improves use of managed
Chain<...>in cases where chain elements may not be known at compile time apart from a prefix setRelated issues, Discord discussions, or proposals
This PR is the formal proposal related to #1091