Ensure shuffled bits get cleared out in "modifying" operations #33
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.
Fixes #32. The core issue here is we're taking a few shortcuts in some operations
like chop, chomp, first, last where we just shuffle the bits around and OR the
new length. The problem is there can be "extra bits" in the inline string that
can then affect operations like
==
. So we need to ensure in these optimized"modifying" operations, these extra bits get zeroed out to ensure a consistent
bit representation.