Add support for Unbox and Unbox_Any opcodes for value-type decompilation #277
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 support for decompiling IL code that contains unboxing operations on value types, enabling two key scenarios that were previously failing:
Issue Description
The decompiler was missing support for
unboxandunbox.anyIL opcodes, causing failures when trying to decompile:Solution
Added support for both unboxing opcodes in
ConvertProcessor.cs:OpCodes.Unbox- Handles unboxing that returns a pointer to the valueOpCodes.Unbox_Any- Handles unboxing for value types or passes through reference typesBoth opcodes are implemented using
Expression.Convert(expression, type)to generate proper expression trees that represent the unboxing operation. The implementation was placed inConvertProcessorsince unboxing is fundamentally a type conversion operation, alongside other conversion operations likecastclassand numeric conversions.Examples
After this fix, the following scenarios now work correctly:
Testing
Added comprehensive test coverage with 7 test cases covering all unboxing scenarios including edge cases with enums, nullable types, and computed properties. All tests pass successfully.
The implementation follows existing patterns in the codebase and maintains full backward compatibility.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.