Specify an upper bound for return value sizes for core::extract_scalar
#346
Conversation
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
manopapad
approved these changes
Aug 24, 2022
marcinz
added
the
category:bug-fix
manopapad
pushed a commit
that referenced
this pull request
Mar 5, 2025
* Support for replicated writes to stores * Remove an obsolete function parameter * Make sure the region requirement is initialized only once * Collective writes are not supported by operations other than tasks * Support for replicated writes to scalar stores * Address review comments * Move the store target check to the right place
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.
This PR is to specify an upper bound for return value sizes for
core::extract_scalar. This also includes a minor optimization for the demux logic that treats future maps of size 1 as futures.