internal compiler error instead of compiler diagnostic - by Aidtopia

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 736931 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 4/14/2012 12:02:57 PM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

I made an error converting a traditional for loop to a std::for_each with a lambda.  Instead of getting diagnostics pointing out the error, the compiler failed with an internal compiler error.  I've reduced the problem to a complete but small sample that reproduces the issue.

This is not a blocking issue, as correcting the source code avoids the internal compiler error, but perhaps this is a mild symptom of a more serious problem.  Also, without the compiler diagnostic, the error can be tough to spot.  Intellisense doesn't seem to know about lambda capture rules, so there are no red squiggles pointing out the error.
Sign in to post a comment.
Posted by Microsoft on 4/16/2012 at 11:41 AM
Hi:
    A fix for this issue has been checked into the compiler sources. The fix should show up in the next release of Visual C++.

Xiang Fan
Visual C++ Team
Posted by MS-Moderator08 [Feedback Moderator] on 4/15/2012 at 6:41 PM
Thank you for submitting feedback on Visual Studio 11 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.