TRIVIAL: Update docs on ProtoReader32 #3488
Open
+2
−1
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.
The doc explaining the reason ProtoReader and ProtoReader32 are separate was inaccurate.
The "tag" methods listed all operate on int's in both cases (ProtoReader and ProtoReader32).
This clarifies which methods actually care about int vs long, and the reason for the divergence between ProtoReader and ProtoReader32.
Its trivial, but its probably worth updating since its pretty important to one of the bigger surprises in the consumer interfaces for this.
From the relevant wire-runtime.api