Dmitry Kurinskiy

Omit function arguments with defaults

1

It's a very convenient pattern to have defaults for arguments. ```python func foo(arg: string = "hello") foo() foo("world") ```

Move integration tests into repo, run them with `aqua run`

1

We may keep the playground or any other kind of integration tests, but it would be nice to have all the main tests in the repo.

Improve errors handling

2

In Aqua, errors are handled with AIR's `xor` instruction, expressed with `if`, `try`, `otherwise` keywords. The problem is that it's hard to implement the fail-fast approach: if the error is...

Resolve match/mismatch with comparison of literals on compile time

1

Remove `if true == false` on compile time.

Parallelism management in Aqua, as in `0.6`, is explicit and is done with `par` (for π-calculus `|`, like `P | Q`) and `co` (π-calculus `null | P`). But this is...

Pattern to join on a portion of peers

3

Consider the following example: ```python res: *string for x

`export` keyword is misleading when we have `import` keyword

1

https://doc.fluence.dev/aqua-book/language/header `exports` in documentation is expressed vaguely: it's unclear that it exports to the host language, it just "exports" However, given that we use `import` expression frequently, intuition hints that...

```python on HOST_PEER_ID: ss: *string ``` This block does nothing. However, now it creates a restriction tag, then wraps its contents with XOR, and so on, which is absolutely meaningless.

When a distributed/p2p application is developed, it needs to be deployed. Deployment to the Fluence network can be described as `app_config.json`. But Aqua language has no bindings to it: it...

When the code is decomposed into Aqua functions, it might happen that the same idempotent function with the same arguments is called many times on the same peer. For example:...