Radosław Rowicki

Regarding where to put it; as a user I completely wouldn't mind if tree-sitter had a flag to produce a multi-crate Rust project with one workspace being the macro lib.

Right now we have a special `void` type for cases where we don't really care what a thing is, but we want to make it unusable (like in the case...

For `clone` you only need arguments. The return type should remain opaque, however. I am thinking of making it either some explicitly "unknown" type such as `void` or `???`, or...

It's a bug caused by running code analysis on desugared code. Nothing to worry about. We'll take a look and fix it soon.

If you are worried though, or if it may impact something serious, you can use `aesophia_cli` with `pp_asm` to check if the function is compiled correctly. The assembler should be...

Will arguments for `init` still make sense when this comes in?

In my opinion it would provide good additional control over the remote calls. Currently we have only small predefined set of named arguments in certain functions – if we introduce...

Any scenario where one would need to protect their calls that uses named args. For example I would expect that ``` con.entr(protected=true, amount=10, duration=20) ``` will verify whether this entrypoint...

Okay, moving it to the interface can do the job. Removing the `consensus-breaking` tag, let this issue focus just on the custom named arguments in the frontend

May be useful: https://www.researchgate.net/profile/Mario-Latendresse/publication/229001057_Simple_and_efficient_compilation_of_list_comprehension_in_Common_Lisp/links/09e4150a68b953e657000000/Simple-and-efficient-compilation-of-list-comprehension-in-Common-Lisp.pdf?origin=publication_detail