Brianna Marshall

@kevinhartman Just getting back into this, sorry for the delayed response. :) > Ah! That's helpful context. I'd tried to suppress a few warnings at one point using `` in...

> Awesome! I will wait for that to go in before fiddling with any warning / error configurations. #807 is merged now. :) > This is the preliminary list of...

This is still an issue, and it makes getting information out of an expression tree much more difficult than it needs to be. For example, this match is several times...

@ScottCarda-MS worked on the lambda lifting, do you know if there's a way to identify a lifted lambda?

The generated code for the array expression is ```csharp (IQArray)QArray.Filled(() => (QArray.Filled(() => 0L, 0L), new QRange(1L, 0L)), 1L); ``` The issue is that `QArray.Filled` returns `QArray`, not `IQArray`. `QArray`...

The problem is that different situations need different actions... sometimes adding type arguments to an identifier is the best option, but other times it is not ideal (when simply using...

From PyQIR's side, I think it would be easiest and consistent with the other instructions to support any value (constant or not constant) as the operands, but you could of...

Value (and its subtypes, including Function, BasicBlock, Instruction, etc.) now has `__str__` which prints the LLVM IR text. It's not as obvious to me what to do for `__repr__`, since...

I think this is likely a bug with Visual Studio's LSP client, so it may need to be fixed on Visual Studio's end. @ricardo-espinoza

I don't think flat vs. hierarchical is the main problem with Q#'s namespace system. For me, the major issue is that namespaces are *open* instead of *closed*, meaning that a...