Clarify VSS expectations on read/write #796
Open
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.
I ended up in a discussion of what "doing a read" in VSS means. In short, as of today that we say that a read returns actual value. This PR suggests to change the wording somewhat, so that a read unless otherwise specified shall return the actual value.
I.e. it is not forbidden by VSS (project) for implementations to have a read-function that returns the desired value instead, but then that must be clearly specified in the corresponding implementation specification.
This shall not impact VISS/VISSR.