WIP: Support List[List[byte, N], N] #17
Open
Conversation
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
1 participant
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.
Current spectests generated by the methodical repo were not covering
ExecutionPayload, so I missed that nested lists were not supported. This commit adds support forList[List[byte, N], N]. 2 things should happen before I remove WIP from the title:Cover List[List] via prysm'sExecutionPayloadtype in spectests.This PR also has a commit removing all the values/funcs/types flagged by the golangci-lint deadcode checker. There are only 2 commits so it may be easiest to review this PR one commit at a time. I am also happy to split off the lint commit into a separate PR.