Skip to content

perf: Exclude Map.Entry from lazy loading to show key:value inline#621

Merged
wenytang-ms merged 1 commit intomainfrom
wenyt/fix-map-entry-display
Mar 30, 2026
Merged

perf: Exclude Map.Entry from lazy loading to show key:value inline#621
wenytang-ms merged 1 commit intomainfrom
wenyt/fix-map-entry-display

Conversation

@wenytang-ms
Copy link
Copy Markdown
Contributor

Map.Entry objects were incorrectly treated as lazy-loading candidates because they are included in COLLECTION_TYPES. This caused the debugger to display entries as 'HashMap$Node@id' instead of showing the actual key:value details inline.

Map.Entry's details computation (getKey + getValue) is lightweight, so eager evaluation is safe and significantly improves UX when debugging large Maps.

Fixes microsoft/vscode-java-debug#1605

Map.Entry objects were incorrectly treated as lazy-loading candidates
because they are included in COLLECTION_TYPES. This caused the debugger
to display entries as 'HashMap$Node@id' instead of showing the actual
key:value details inline.

Map.Entry's details computation (getKey + getValue) is lightweight,
so eager evaluation is safe and significantly improves UX when debugging
large Maps.

Fixes microsoft/vscode-java-debug#1605

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@wenytang-ms wenytang-ms merged commit 26b05eb into main Mar 30, 2026
4 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.

Map<Integer, Double> displays badly

2 participants