Closed vsfeedback closed 3 weeks ago
@AlekseyTs this was moved from an internal feedback ticket that is now closed. It has no other useful info (no dumps). If we can't determine what is causing this bug from the stack then we should just close out and wait for another report.
it's unclear why this is even assigned to compiler. AFAICT< the stack indicates a bug on the IDE side in ExpressionCodeGenerator.GetStatementOrInitializerContainingInvocationToExtractedMethodAsync
where we're likely doing an invalid ReplaceNode causing a crash in the replacer when it cannot fit hte replaced node into the location we're replacing. @jaredpar feel free to reassign to ide here.
It is hard to say what is going on here. Quite possibly the "Extract Method" refactoring places the call at the position where a type is supposed to be syntactically.
Closing out as this was rewritten and i don't see prism hits for this.
This issue has been moved from a ticket on Developer Community.
[severity:It bothers me. A fix would be nice]
Original Comments
Feedback Bot on 11/1/2021, 00:41 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Original Solutions
(no solutions)