Mine Starks
Mine Starks
We _could_ have one big giant `expect![]` that verifies the result of dynamically concatenated program outputs, right? It's not obviously clear to me which way's better at the moment, you're...
**CONTRIBUTORS PLEASE READ** Welcome! Here are some details to get you started. ### Detailed issue description This feature can be implemented either in the VS Code Resource Estimation panel, or...
@nirajvenkat I want to assign this issue to you (for unitaryhack). Could you please comment on this issue so GitHub will let me assign to you?
Partially addressed in #1947 (unit tests for completions from package dependencies), but not for notebooks yet.
Draft PR wiring up basic implementation of P1 features in VS Code and the playground: #364
> @minestarks -- is #1038 going to unblock LSP support, or are there other changes required? @sezna well, we'd have to implement an LSP server... but if you're asking if...
Closing as completed. The unchecked items in the original description are currently out of scope.
@swernli why, what do you have in mind when you say "live resource"? Do we have direct links to the `main` of this repo from documentation?
Not sure if was meant to be covered in this issue, but another concern is that errors contain `SourceMap` offsets which do not get properly mapped to file offsets. The...
> _Change in memory usage detected by benchmark._ > > ## Memory Report for [6fbbec5](https://github.com/microsoft/qsharp/commit/6fbbec5027789cfc5e384b13e4eb61f410f50b52) > Test This Branch On Main Difference > compile core + standard lib 17940700 bytes...