-
Notifications
You must be signed in to change notification settings - Fork 37
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
migrate compat to trace_decoder crate #308
migrate compat to trace_decoder crate #308
Conversation
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.
I like this change, and the rationale, but trace_decoder::types
is going away pretty soon: #309.
Can you break this out into a compact
micro-crate, with publish = false
, and we can decide on it's final resting place when the dust settles?
2e2adb0
to
e86adff
Compare
455359e
to
1dcbf4e
Compare
5a9c290
to
3b83313
Compare
@frisitano Could you rebase so that we can merge? |
27b97a5
to
254491b
Compare
254491b
to
10702d1
Compare
done. |
This PR proposes that we migrate the
Compat
trait totrace_decoder::types
. The rationale behind this migration is such that if there are clients that alloy based which want to integrate with the trace protocol they should not have to import therpc
crate to get access to theCompat
trait and associated conversions. A concrete example of this is the integration ofreth
which isalloy
based.