Mark Koch
Mark Koch
But should we expose this to the user? Having to pass the state around seems very cumbersome for things like `result` or `panic`
Some thoughts on how to do this: * Add an extendable type of `SideEffect` that captures different kinds of side effects (e.g. `PRNG`, `IO`, ...) * Each builtin function specifies...
We can now do this without custom checkers! Closing in favour of #1157
Apologies, totally forgot about this PR 😅
This seems to be a problem with checking that `__setitem__` has the correct signature: Passing `nat` instead of `int` seems to confuse the checker...
Smaller reproducer: ```python @guppy def foo(xs: array[qubit, 10], i: nat) -> None: h(xs[i]) ```
> Update this to report all the error messages we can find I think we should only focus on the multiple spans part for now. Reporting multiple errors requires us...
See tracking issue #535
Closed by #547
Reflecting on this, I think it's fine to keep the error since it actually matches Python's behaviour: ```python x = 0 def foo(b: bool): if b: x = 1 return...