Conditional compilation for individual capabilities #996
Assignees
Labels
Comments
|
@sezna if you start working on this, could we sync to talk through some options to make sure we can use it in the multiple scenarios conditional compilation would be useful? |
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 8, 2024
) In order to support adaptive profile selection in VS we have to add `Adaptive` as a compilation attribute in the std lib. This is a workaround until we design a full solution to address #996. This PR adds adaptive as a profile. Functionality to enable adaptive profile VSCode is hidden behind a config value, as is using the preview QIR code generation from VSCode. QIR generation for Adaptive/Unrestricted from Python will continue to raise exceptions. Adaptive is a profile allowed in the Python APIs, but warnings will be issued to users indicating that this functionality is in preview. The language service will surface RCA errors in VSCode and Python, but not the Notebooks (will be handled in a follow up PR). Other integration features are being tracked in #1294 and this PR is not expected to have all functionality enabled. --------- Co-authored-by: Alex Hansen <[email protected]> Co-authored-by: Stefan J. Wernli <[email protected]> Co-authored-by: Mine Starks <[email protected]>
|
@swernli says we've done this, he will verify. |
|
Fixed by #1393 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently support
@Config(Base)and@Config(Full). But, eventually, we will want to conditionally compile code for individual capabilities. See #882 for additional context.This syntax could also be used to opt a Q# project in to new language features, like new UDT syntax. Similar to Rust's
#!or Haskell's language extensions. See #543 for more context on that.The text was updated successfully, but these errors were encountered: