DumpMachine
output in Python and console should be empty with no qubits allocated
#1984
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change updates the display of quantum state when no qubits are allocated to show a message rather than the same output as one qubit in the zero state. This matches the updated debugger behavior. Note that I've tried to ensure this is NOT a breaking change for consumers of the WASM/npm package by extending the data type rather than changing the behavior or contents of existing fields, and verifyied this by leaving the dev playground unchanged and confirming it preserved the old behavior there (playground will be updated in a follow up PR and is tracked by a separate issue).
Fixes #1961