Skip to content

Reuse EmptyObject for HCS NUMA configuration - #41768

Merged
Ben Hillis (benhillis) merged 1 commit into
microsoft:masterfrom
benhillis:benhillis/follow-up-vnuma-empty-object
Oct 2, 2026
Merged

Ben Hillis (benhillis) merged 1 commit into
microsoft:masterfrom
benhillis:benhillis/follow-up-vnuma-empty-object

Conversation

@benhillis

Copy link
Copy Markdown
Member

Summary

Reuse the shared EmptyObject JSON type for the HCS NUMA configuration instead of maintaining an identical local type and serializer.

Follow-up to OneBlue's suggestion in #41741: #41741 (comment)

Validation

  • Full x64 Debug build
  • FormatSource.ps1

Copilot AI balanced review requested due to automatic review settings October 2, 2026 01:08
@benhillis
Ben Hillis (benhillis) requested a review from a team as a code owner October 2, 2026 01:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟢 Approval recommended

The focused refactor preserves existing serialization behavior without unresolved issues.

Review effort: Balanced
Findings: None

What changed in this PR

Reuses the shared JSON empty-object type for HCS NUMA configuration while preserving {} serialization.

Changes:

  • Removes the redundant NUMA type and serializer.
  • Uses wsl::shared::EmptyObject for optional NUMA topology.
File Description
src/​windows/​common/​hcs_schema.h Reuses the shared empty-object representation for NUMA.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@benhillis
Ben Hillis (benhillis) merged commit 59d1eaa into microsoft:master Oct 2, 2026
9 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.

3 participants