Brianna Marshall
Brianna Marshall
The `New` methods defined in https://github.com/microsoft/qsharp-compiler/blob/main/src/QsCompiler/Core/ConstructorExtensions.fs can't be accessed from C#. This is problematic when changing the fields of a record, since the `New` methods can go through a deprecation...
The `NoWarn` SDK property is not fully supported by the Q# SDK and the language server. While it seems like MSBuild recognizes it and hides matching warnings, `NoWarn` is not...
From microsoft/qsharp-language#59: > I was trying to implement the carry lookahead adder from https://arxiv.org/pdf/2004.01826.pdf . it has a step described like this: > >  > > As you can...
From microsoft/qsharp-language#132: > I'd like to be able to write this: > > ``` > for k in 0L..15L { > ... > } > ``` > > Currently this...
Namespaces don't make sense in Q#. Their only benefit is in organization and avoiding name conflicts, but they don't help you define abstractions or use encapsulation/information hiding. A module system...
From microsoft/qsharp-language#58: > **Suggestion** > > When writing arithmetic code, there is a tendency to repeat the same method multiple times based on whether certain inputs are quantum or classical....
Patterns in Q# can be extended to support UDTs, literals, etc. Match expressions would be useful for branching on an integer or string value, or a value of a sum...
Q# needs sum types (tagged unions, discriminated unions, Rust-style enums, etc.). See microsoft/qsharp-language#51, microsoft/qsharp-compiler#406.
From microsoft/qsharp-language#149: > **Is your feature request related to a problem? Please describe.** When writing a polymorphic function in Q#, the type variables are fully general. They are opaque types...