-
Notifications
You must be signed in to change notification settings - Fork 16
feat: support more map key type #67
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
Open
WangFengtu1996
wants to merge
4
commits into
injae:main
Choose a base branch
from
WangFengtu1996:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fd59388
feat: support more map key type
WangFengtu1996 210eb33
Move to_string function to detail namespace
WangFengtu1996 7a80c15
Refactor serialize and deserialize functions <=> std::string
WangFengtu1996 ab05778
Replace from_string with deserialize in serializer
WangFengtu1996 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems that we may need to revisit the current approach for implementing
T <-> stringconversions in the serde core.There appears to be a small issue with the direction I suggested previously. After giving it some more thought, I think the approach where each adapter is responsible for its own implementation—similar to the adapter you implemented in the previous PR—might be a better and cleaner solution overall.
With the current approach, I see a couple of concerns:
Implementing this would require introducing STL containers into the serdepp core.
I do understand why using
unordered_mapis effectively unavoidable in this case(according to the C++ specification, when
T = M<K, V>, we can extractKandV, but notMitself, which makes it impossible to construct something likeM<string, V>).That said, serdepp currently tries to intentionally avoid using STL containers in the core library.
In the C++ ecosystem, it’s fairly common to rely on spec-compatible custom implementations instead of STL containers, often due to performance considerations.
This approach would make serdepp less adapter-neutral.
Serdepp was originally designed with the goal of supporting adapters that are not necessarily JSON-compatible.
From that perspective, implementing it this way might go slightly against that original intention.
In summary:
It might be better to delegate the responsibility for
T <-> keysupport to the adapter itself.Rather than adding a separate
to_stringspecialization in the core, we could rely on the existing serdeserializeanddeserializeimplementations that adapters already provide.Additionally, it could be helpful to introduce shared utility functions for this behavior, so that different adapters can reuse the same logic where appropriate.
Additionally, since we’re currently using squash merges, it should be fine to make the changes in this PR.