microsoft / microsoft/MIEngine
Type template parameter not stringified
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 859
- Forks
- 233
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 3
Description
Expansion in such a form
<ExpandedItem Condition="which() == 0" Optional="true">( $T1 *) &rep_.data</ExpandedItem>
only works in cppvsdbg. $T1 is a type template parameter (rather than a non-type template parameter) and the full expansion should be treated as a cast. The expression does evaluate correctly in evaluator.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies the evaluator and cppvsdbg behavior as the relevant entry points; begin by tracing how type template parameters are stringified in the evaluator and compare that path with cppvsdbg. Done means the ExpandedItem cast form works consistently beyond cppvsdbg while preserving the evaluator’s currently correct result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100