Fixed serialization of type requiring "size" information in uint32_t or uint64_t instead of size_t, added options::force_aligned_access
#45
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 pull request addresses the issue identified in #43 regarding the serialization of size information using
size_t
type, which is not architecture-agnostic.To ensure consistent serialization across different architectures, the size information for strings, vectors, and other types that require a size attribute is now serialized using a type explicitly defined in alpaca::detail::size_t_serialized_type (uint32_t or uint64_t).
This change guarantees uniformity in the serialized data, irrespective of the platform.
I also aligned the tests and I added a set of test generated by chatgpt.