Bug/cell brand #2011
Closed
Bug/cell brand #2011
Conversation
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
…in case of OpaqueRef<Cell<T>>
Contributor
Author
|
closing since berni fixed this issue in a different PR another way. |
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.
Exploration of how to fix bug with conflicting CELL_BRANDS in OpaqueRef<Cell>
Summary by cubic
Fixes a type conflict in OpaqueRef<Cell> where [CELL_BRAND] collisions reduced the type to never. OpaqueRef now skips symbol keys to prevent brand conflicts, restoring valid get/set access on cells.
Written for commit dd12a0d. Summary will update automatically on new commits.