-
Notifications
You must be signed in to change notification settings - Fork 254
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
remove solana-sdk from rpc-client #3833
Conversation
If this PR represents a change to the public RPC API:
Thank you for keeping the RPC clients in sync with the server API @kevinheavey. |
4e72201
to
fbcf2e5
Compare
3f21340
to
5ce400a
Compare
1578b8b
to
282e597
Compare
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.
For fun, I checked the build difference from this PR, and I was averaging ~14.5s for cargo clean && cargo build
, and master gives double the number of crates to build, but averages ~18.5s build time.
Anyway, looks great!
@@ -1355,11 +1346,11 @@ impl RpcClient { | |||
/// and the transaction failed, this method returns `Ok(Some(Err(_)))`, | |||
/// where the interior error is type [`TransactionError`]. | |||
/// | |||
/// [`TransactionError`]: solana_sdk::transaction::TransactionError | |||
/// [`TransactionError`]: solana_transaction_error::TransactionError |
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 didn't realize how smart this is -- it actually currently resolves back to solana_transaction_error::TransactionError
🥳
Either way, it's definitely better to use the base import
Problem
This crate can compile faster without solana-sdk
Summary of Changes
Remove it and replace with constituent crates as appropriate
This branches off #3634 so that needs to be merged first (update: done)