-
Notifications
You must be signed in to change notification settings - Fork 104
Support ObjectMap for std::stack, std::queue, std::priority_queue #1488
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
leekillough
wants to merge
5
commits into
sstsimulator:devel
Choose a base branch
from
leekillough:objectmap_adapter
base: devel
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 1 commit
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
21f5394
Add missing #include <memory>
leekillough 6d9527e
Support ObjectMap for std::stack, std::queue, std::priority_queue
leekillough 7a954fb
Set read-only mode only for std::priority_queue
leekillough 6dc1f9f
Merge remote-tracking branch 'sstcore/devel' into objectmap_adapter
leekillough c1dbb2b
Merge branch 'include_memory' into objectmap_adapter
leekillough 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's read-only now. Question: Do we really need to pass other
optionsdown, or can we just ignoreoptionsand passSerOption::map_read_only? (In that case, we probably don't need to passoptionsin theSST_SER()call below either, and we can sayUNUSED(options).)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.
For now, I believe read-only only affects fundamentals because it is not applied to members of a class. We'll need to figure out how we want this to apply to data members. We may need to track it as part of the path. I could see accessing an object through different paths where on path is read-only and the other isn't. It's an interesting problem.
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.
Yes, but my question was mainly about other options when serializing, say
std::priority_queue. Are there any serialization options when serializingstd::priority_queuewhich need to be passed when serializing the underlying container, or can we just ignore all serialization options passed when serializingstd::priority_queue?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.
I add read-only for
std::priority_queuenow, but I pass the adapter serialization options as-is to the serialization of the underlying container.