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

Cleanup and function/struct access control #35

Merged
merged 1 commit into from
Feb 12, 2025
Merged

Conversation

dpp
Copy link
Contributor

@dpp dpp commented Feb 11, 2025

💻 Description of Change(s) (w/ context)

Cleaned up some pub struct elements that needed to be private. Some other method moving around

Made route creation public

🧠 Rationale Behind Change(s)

Improving library ergonomics

📝 Test Plan

Passes existing tests

…ther method moving around

Signed-off-by: David Pollak <[email protected]>
Comment on lines +113 to +116
pub fn get_cluster_file_hash(&self) -> u64 {
self.cluster_file_hash
}

Copy link
Contributor

Choose a reason for hiding this comment

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

Does the indirection get us anything if we're not relying on the ABI?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Part of it is my Java roots... getters everywhere!

Part of it is figuring out how to abstract the data structure. Big Tent is a library and at some point we'll have to
stabilize the API... having pub stuff on structs makes API evolution harder...

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, a little harder. My experience is that most evolutions of note reshape it in more fundamental ways anyway and it comes out in the wash. (And breaking isn't the worst thing, just have to plan and communicate it a bit)

@dpp dpp merged commit c974543 into main Feb 12, 2025
1 check passed
@dpp dpp deleted the dpp/pub_build_route branch February 12, 2025 13:16
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