Clarify the required behavior of concurrent calls#142
Merged
Conversation
athoelke
added
clarification
Ryan-Everett-arm
left a comment
Ryan-Everett-arm
left a comment
There was a problem hiding this comment.
It was a good idea to add an example here, the intuition of concurrency constraints can be difficult to understand. I'm not sure if the proposed constraint will be interpreted as intended, though; see my comment below.
* Provide general caveat about consistency and resource-related errors * Add some structure to the concurrency rules
gilles-peskine-arm
approved these changes
Jan 11, 2024
3 tasks
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
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.
Relax/clarify the statement regarding the required behavior of implementations that support concurrent execution of calls to the API.
Fixes #134