We describe how to generate a repro for the kind of issue you've found, and how to send your report to the product team. In the sections below, you'll read about what makes a good report. It helps us determine whether it affects other versions of the compiler, and to diagnose its cause. This information lets us quickly verify that the problem exists in our code and isn't local to your environment. And it should include a repro, a complete test case we can use to reproduce the problem on our own machines. It should have all the details about how you build your program. The best way to let us know about a problem is to send us a report that includes a description of the problem you've discovered. When the issue is in our documentation, we want to know about that, too. ![]() If you find problems in the Microsoft C++ compiler (MSVC), the linker, or other tools and libraries, we want to know about them.
0 Comments
Leave a Reply. |