Use write_all for fixed-size payloads in R1CS writer #383
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 change replaces two calls to write(...) with write_all(...) when writing fixed-size payloads:
The paired reader uses read_exact for these fields, so write(...) risks short writes and corrupting the bytestream. Using write_all(...) guarantees the full buffer is written, ensuring consistency with the reader and with the rest of the module, which already uses write_all for fixed-size data.