feat: add op for creating new/empty list #1729
Draft
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.
Constants cannot refer to type variables, so you can't have a constant for an empty
List<T>
...ListOp::new
to handle thispub(crate)
for now) for whether a Type, TypeArg or ExtensionSet contains variables.I'm a bit, ugh, do we have to do this; when we move to hugr-model, we'll have a better way, so we'll end up redoing this again. Hence I've not written any tests yet, but will do if we think we want this....?