-
Notifications
You must be signed in to change notification settings - Fork 224
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
Proposition of changes into Casper Types to support a Rust SDK for 1.6 #4348
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.
Similar to my comments on the related PR against the casper-client
, I think it makes sense to approve these to get the SDK out for 1.6. However, I would love to see this feature changed in 2.0 to be additive.
Additionally, I would like to see the lints fixed along with whatever is causing the drone to fail on cargo-test-pr.
…SDK-1.6 # Conflicts: # hashing/Cargo.toml # types/CHANGELOG.md
4445: Split 'std' feature into 'std' and 'std-fs-io' in casper-types r=Fraser999 a=Fraser999 This PR restricts the functionality of the `std` feature of `casper-types` to exclude methods unsuitable when compiling the crate to Wasm. It also adds a `std-fs-io` feature to include this functionality. It borrows the concept and supersedes #4348 by `@gRoussac.` casper-ecosystem/rustSDK#8 casper-ecosystem/rustSDK#10 Co-authored-by: Fraser Hutchison <[email protected]>
Please consider the following when creating a PR:
This PR intends to pull changes made for the Rust SDK. It is adding a
std-fs-io
default feature and thus adds several methods or expose them accordingly to be able to compile the SDK into a wasm file.check
casper-ecosystem/rustSDK#8
casper-ecosystem/rustSDK#10
This code is intended to go into 1.6 version for the 1.6 ready version of the SDK.