Repository navigation
refactor: re-export the core MARF types at the stacks-marf root - #7752
Open
rob-stacks wants to merge 1 commit into
Open
rob-stacks wants to merge 1 commit into
rob-stacks wants to merge 1 commit into
Conversation
cylewitruk-stacks
approved these changes
Oct 16, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Addresses @cylewitruk-stacks' review comment on #7697: having the core types under a marf module inside the stacks_marf crate is redundant, so they should live at, or be re-exported from, the crate root.
Callers can now write stacks_marf::MARF instead of stacks_marf::marf::MARF. It's additive: the existing stacks_marf::marf::… paths keep working, so no call sites change here. They can migrate whenever they're next touched.