-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chain_getBlock extrinsics encoding #1024
Merged
tadeohepperle
merged 8 commits into
master
from
tadeo-hepperle-chain-get-block-extrinsic-decoding
Jul 13, 2023
Merged
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
ebd7360
deserialize without decoding
tadeohepperle eeefa5c
change decoding approach
tadeohepperle daef05e
Merge branch 'master' into tadeo-hepperle-chain-get-block-extrinsic-d…
tadeohepperle 04f74fd
fix tests
tadeohepperle 1cc8f55
decode without allocating
tadeohepperle a343001
strip compact prefix
tadeohepperle d6d502b
cargo fmt
tadeohepperle 743e73a
nit adjustment
tadeohepperle File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here and in the
.position(..)
thing below, we could avoid the allocating by instead decoding theCompact<u64>
off the front of the bytes and then seeing how many bytes were consumed in doing this.(I say "avoid allocating" but this was copying the bytes into an
Arc
before, so either way you may allocate, but at least have the chocie of exactly where)This "compact length" value (or in other words an "extrinsic_start_index" could be saved if useful in
ExtrinsicDetails
so that it's easy to get the rest of the bytes from it when needed.I'd have to look at the code in more detail to see what the
Arc
was used for before and whether it's then good to keep it, or whether perhaps theVec<ChainBlockExtrinsic>
inExtrinsics
could be instead something likeArc<[ChainBlockExtrinsic]>
so that we don't allocate at all when weiter()
over the extrinsics :)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could also give the
ExtrinsicDetails
an explicit lifetime that is bound by the lifetime ofExtrinsics
. This way we can degrade the bytes field ofExtrinsicDetails
tobytes: &[u8]
instead ofbytes: Arc<[u8]>
where the slice points to thei..
bytes of the Vec of the respective ChainBlockExtrinsic, where i is the compact encoded length. This also avoids allocation. I am not sure though if the Arc was necessary somewhere.