Mark Koch

Longer term we should just get rid of `__hasnext__` and make `__next__` return an option type. However, this requires enums or some other ways to encode sums in the language....

From the Guppy side, the following interface might be nicer than the detached `new_wasm` method: ```python @guppy.wasm_module(file=".../wasm_decoder.wasm") class MyWasmDecoder: @guppy.wasm def add_one(self, x: int) -> int: ... @guppy.wasm def add_syndrome(self,...

We currently don't support static methods, but it wouldn't be hard to add them. But I think the `self` argument is actually one of the benefits since it makes the...

Duplicate of #772

> are you opposed to adding a dedicated decorator for this? If we use this in all examples then that's what people will copy and use themselves. So I think...

See this guide for how to do LSPs for embedded languages: https://code.visualstudio.com/api/language-extensions/embedded-languages

Note that we still need to generate Hugr discards which is not entirely trivial when considering nested structs, arrays, and lists. Also, would this be a special case for the...

> Otherwise I think things are likely to get messier rather than tidier...unless I'm missing something? Agreed, implementing linear effect tokens will definitely be more difficult and most likely more...

More radical proposal: Every single argument function should automatically map over arrays?

One interesting detail: We need to prevent (mutually) recursive aliases: ``` Alias1 = guppy.type_alias("Alias2") Alias2 = guppy.type_alias("Alias1") ``` We can probably do something similar to what we use to detect...