Mine Starks comments

Results 36 comments of


                                            Mine Starks

Error: No Project. in 'Object.ThrowNoProject' during 'getApplicableRefactors'

I have a repro in #35559

Allow implicit top-level namespaces when parsing files

@sezna should we update our samples to eliminate namespace declarations, since that's the recommended syntax now?

Lint rule: `operation`s that don't manipulate quantum state can be `function`s instead

@Manvi-Agrawal that got me scratching my head for a bit! But I figured it out. The compiler should return an error for a `function` that calls an `operation` . So,...

Python: Long gate names are rendered poorly in ASCII art circuits

@Pulkit1822 apologies for missing your post. It's been a while so hopefully you're still interested -- I'd say this is a fairly low-priority bug, and with no-one that I know...

Add support for CodeActions in the Language Service

Forgot to mention, you'll want to wire this up in the Playground using the Monaco editor as well. Its APIs are very similar to VS Code's, so hopefully it shouldn't...

Lint rule: When qubit reuse is not supported, prefer `MResetZ` over `M`

Good questions - this originally came from @swernli so I'll let him weigh in.

Lint rule: When qubit reuse is not supported, prefer `MResetZ` over `M`

@swernli do we have any precedence for looking up the `ItemId` of a specific std function in the HIR by name? Thinking about how we'd identify calls to `MResetZ`. We...

Provide a mechanism for defining simulator-only implementations of callables designed to be intrinsic for code generation

> * Another benefit of attribute vs new "body" syntax is that it's easier to quickly turn it off and on, as you only need to add/remove or comment/uncomment one...

In Jupyter notebook, if simulation ended with runtime exception, allocated qubits are not cleared up

@swernli I can see how the current behavior is by design, and technically, continuing to execute statements after a runtime error is inadvisable -- but this is super common to...

In Jupyter notebook, if simulation ended with runtime exception, allocated qubits are not cleared up

I think the feature suggestion here is essentially "stack unwinding" - making `fail`s behave like exceptions do, deallocating resources as the stack gets unwound. Currently `fail`s in Q# _don't_ have...