chore(storable): revert unbounded 2-tuple Storable impl#436
Merged
Conversation
…)" This reverts commit bbc94de.
maksymar
approved these changes
Apr 22, 2026
|
|
|
|
|
|
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
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
Storablefor unbounded 2-tuples.todo!()panics that fail loudly instead of silently mis-decoding data.Motivation
As noted in this comment by @maksymar:
The 2-tuple now carries two completely different wire formats (bounded vs unbounded), so a user who flips a type's
BOUNDfromBoundedtoUnboundedwill silently mis-decode existing data. The 3-tuple doesn't have this problem since it uses one unified wire format for both variants.Reverting to
todo!()is safer — it fails loudly rather than risking silent data corruption.🤖 Generated with Claude Code