Skip to content
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

[refactor] move fastx core types and authority into separate crates #35

Merged
merged 1 commit into from
Dec 8, 2021

Conversation

sblackshear
Copy link
Collaborator

@sblackshear sblackshear commented Dec 8, 2021

Separate out the fastx base types (used by clients, the adapter, authority, ...) and the authority code into separate Rust crates. A future PR connecting the fastx-programmability and fastpay-core crates leads to a cyclic dependency without this refactor.

@@ -59,7 +58,6 @@ pub fn address_to_object_id_hack(address: FastPayAddress) -> ObjectID {
.expect("An address is always long enough to extract 16 bytes")
}

#[cfg(test)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why removing all of the cfg test annotations?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function is now in a different crate from some of its callers, but code gated by cfg(test) is not gated outside of its declaring crate: rust-lang/cargo#8379

Separate out the fastx base types (used by clients, the adapter, authority, ...) and the authority code. A future PR connecting the `fastx-programmability` and `fastpay-core` crates leads to cyclic dependencies without this refactor.
@sblackshear sblackshear merged commit 7db00b8 into MystenLabs:main Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants