feat: support compact_str for oapi #1024
Merged
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.
Description
This pull request introduces support for the compact_str crate in the salvo web framework’s OpenAPI integration. The use of compact_str provides an efficient and lightweight alternative to String, particularly beneficial for scenarios involving small strings, reducing memory overhead without sacrificing usability.
Key Changes
Why This is Needed
The compact_str crate offers significant performance and memory usage advantages for string-heavy applications. This addition makes salvo more flexible and optimized for use cases where efficient memory utilization is critical, aligning with modern Rust best practices.