Fix reverseChunked(by:)
Method Implementation
#465
Merged
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.
Summary
This pull request is being made to resolve an inconsistency found in the reverseChunked(by:) method located within the Collection extension. The intended functionality of the method is to divide a collection into chunks of a given size, where, if the collection is not evenly divisible, the first chunk will be smaller. Instead of this expected behavior, the current implementation produces incorrect results, with the first chunk not being the smallest when required and subsequent chunks varying incorrectly in size.
Example
Here are concrete examples that demonstrate the problem with the reverseChunked(by:) method's current implementation:
Example 1:
Example 2:
Impact of Changes
The changes introduced by this pull request will resolve the crashing issue in the PostgresNumeric(decimalString:) initializer. The crash is currently caused by the improper handling of string to numeric conversion when the string is split into chunks using the reverseChunked(by:) method.