feat: IntoLogData #666
Merged
feat: IntoLogData #666
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
mattsse
approved these changes
Jun 17, 2024
DaniPopes
requested changes
Jun 17, 2024
DaniPopes
approved these changes
Jun 18, 2024
klkvr
pushed a commit
that referenced
this pull request
Aug 4, 2024
* feat: IntoLogData * fix: add encode_log_data and encode_log * test: update to check re-encoding
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.
Motivation
Groundwork for alloy-rs/alloy#623
Adding this conversion trait allows us to bound receipt log vectors in more meaningful ways
Solution
Introduce trait for types which can be infallibly converted into LogData
PR Checklist