Require iodata ~> 0.9 - #17
Merged
Merged
Conversation
## Why iodata 0.8.0 fixed iolists silently returning truncated data for out-of-range reads, and 0.9.0 made nested-iolist traversal linear instead of quadratic — both directly on the paths Flatbuffer uses for iodata buffers. Older 0.7.x can hand back short reads without error, so raise the floor rather than just the lock. ## What - mix.exs: iodata ~> 0.7 becomes ~> 0.9; mix.lock pins 0.9.0. - Full suite plus the flatc integration tests pass against 0.9.0. Claude-Session: https://claude.ai/code/session_014wfX6262n6A6qBPCXEo6Gz
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
iodata 0.8.0 fixed iolists silently returning truncated data for out-of-range reads, and 0.9.0 made nested-iolist traversal linear instead of quadratic — both directly on the paths Flatbuffer uses for iodata buffers. Older 0.7.x can hand back short reads without error, so this raises the requirement floor rather than just the lock.
What
mix.exs:iodata ~> 0.7→~> 0.9;mix.lockpins 0.9.0.flatcintegration tests pass against 0.9.0. All other deps (benchee, castore, ex_doc, excoveralls) are already at their latest versions.https://claude.ai/code/session_014wfX6262n6A6qBPCXEo6Gz