Brianna Marshall

I'm not sure what the flat QASM (`scaffold.sh -f`) output should be exactly, but the OpenQASM (`scaffold.sh -b`) output has a similar problem: ``` OPENQASM 2.0; include "qelib1.inc"; qreg q[3];...

> Perhaps you're looking for `Module::get_global` which takes the name by string or `Module::get_first_global`? The name or index of the global isn't known since you're starting from only the argument...

Note that just having .NET 5 installed is enough to break the language server, even if I also have .NET Core 3.1 installed, and the Q# project is targeted for...

Possibly related issues: * microsoft/MSBuildLocator#92 * dotnet/roslyn#49248 * dotnet/tye#699

A workaround is to add a `global.json` file to your Q# project, or to any parent directory (such as your user directory), that sets the .NET SDK version to 3.1:...

I think if we can't find any other solution to support .NET 5 and .NET Core 3.1 simultaneously, then adding `global.json` to the project template would make sense. But it...

I'm not sure if the fix for microsoft/MSBuildLocator#92 means that .NET Core 3.1 SDK will be automatically selected without a global.json, or if it will actually work without .NET Core...

This is blocked until our QDK build pipeline is updated to build with .NET 5.

I don't think it's a bug with the implicit scope per se, but it is a bad interaction between the implicit scope and the scope rules for repeat-until. The example...

Another way to think about this from a design perspective is that we have two features that are not orthogonal, which led to an unexpected interaction with a third feature....