-
Notifications
You must be signed in to change notification settings - Fork 173
Changing some errors to warnings and vice versa #643
Conversation
rmshaffer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that this should also resolve microsoft/iqsharp#266 without any additional changes in IQ#. I will test that after this is merged.
Co-authored-by: Guen P <guenp@microsoft.com>
…arp-compiler into beheim/diagnostics
|
I've looked into the CI failure here a little bit, specifically, the error in the IQ# test called In this test, we attempt to compile this Q# source file as a library. Specifically, the The compilation produces the new Is there something about changing the For reference, the generated C# code from the above Q# compilation is pasted below. Does this look as expected? |
|
@bettinaheim Is my investigation above is enough for you to figure out what's going wrong here? Please let me know if I can provide any more information to help diagnose. Please note that microsoft/iqsharp#266 is a relatively bad bug that will be fixed by this change, so from that perspective it would be great to get this addressed soon. |
"Specifically, our call to ProjectManager.LoadReferencedAssemblies() returns an empty dictionary" |
That's correct. Without this change, the reference loads correctly and the test passes.
There are no compilation errors, and the only warning is the expected To help compare before/after, here is a diff of the C# compilation output before (left) and after (right) this change: You can see that with this change, the compilation is considerably different. I assume that's because the rewrite steps are actually running, now that the |
@rmshaffer It looks like the problem is indeed that this is the first time now that an autogenerated operation (which has not position information) is deserialized via the header attributes. I am looking into it. |
The warning for reserved underscore patterns is now an error.
The error for entry points in libraries is now a warning (addressing #571).