Skip to content

test: IM value remains forced after refreshing var#303

Merged
alt-romes merged 1 commit into
masterfrom
wip/romes/debug-view-2
Apr 29, 2026
Merged

test: IM value remains forced after refreshing var#303
alt-romes merged 1 commit into
masterfrom
wip/romes/debug-view-2

Conversation

@alt-romes

Copy link
Copy Markdown
Collaborator

Unlike in #301, the DebugView instance for IntMap displays as a
debugFields value the actual heap referenced stored in the IntMap.

This means that forcing an IM value once, then displaying with DebugView the
same IntMap a second time, should display the IM value still forced.
Because the heap reference is the same.

This commit just adds a test which asserts this (it wasn't tested
before).

Unlike in #301, the `DebugView` instance for `IntMap` displays as a
`debugFields` value the actual heap referenced stored in the `IntMap`.

This means that forcing an IM value once, then displaying with `DebugView` the
same IntMap a second time, should display the IM value still forced.
Because the heap reference is the same.

This commit just adds a test which asserts this (it wasn't tested
before).
@alt-romes alt-romes merged commit bb5a0f9 into master Apr 29, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant