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

Reduce unnecessary public visibility of some SVM structs and APIs #4308

Merged
merged 3 commits into from
Jan 7, 2025

Conversation

pgarg66
Copy link

@pgarg66 pgarg66 commented Jan 7, 2025

Problem

Some structs and APIs in SVM do not need to be pub.

Summary of Changes

Reduce the visibility to private or pub(crate).

Fixes #

@pgarg66 pgarg66 marked this pull request as ready for review January 7, 2025 18:10
@pgarg66 pgarg66 requested a review from a team as a code owner January 7, 2025 18:10
@pgarg66 pgarg66 merged commit 5bcdd49 into anza-xyz:master Jan 7, 2025
40 checks passed
@pgarg66 pgarg66 deleted the limit-pub branch January 7, 2025 21:32
@@ -11,7 +11,7 @@ use {
};

#[derive(Debug, Default, Clone, serde_derive::Deserialize, serde_derive::Serialize)]
pub struct MessageProcessor {}
pub(crate) struct MessageProcessor {}

Choose a reason for hiding this comment

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

I believe some people use MessageProcessor::process_message in their libraries, such as LiteSVM. Any objection to keeping this one public, and just keeping it within the "not guaranteed under SemVer" band?

cc @kevinheavey

Choose a reason for hiding this comment

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

I would like MessageProcessor to be pub yes. But I guess I was already planning on copy-pasting it since litesvm doesn't use anything else from solana-svm

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.

4 participants