Introduce Custom Prelude for Improved Code Organization and Convenience #19
Conversation
This file contains 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
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.
Motivation:
issue #16
Currently, our codebase has scattered import statements across modules, leading to a lack of consistency and increased verbosity. This pull request introduces a custom prelude to centralize frequently used imports, improving code organization and developer experience.
Changes Made:
The creation of the prelude.rs file.
Re-exported items from various modules.
Any significant changes to existing modules or files.
Impact:
These changes are backward-compatible and should not impact existing functionality. Developers using our crate can seamlessly transition to the new prelude for a more streamlined import experience.