Simon Wegendt

Depends on #19

@32leaves: > The main issue here is that at the moment we cannot ship types, functions, any Mita code as part of a library if that Mita code requires code...

@priyashiyadav: - implement modality `connected : bool` - add exception `NOT_CONNECTED` or similar - throw exception on read/write on not connected BLE

These values would be used to initialize the BLE storage variables. Maybe „init“ would be a better name?

> this should be fixed in #320 Sadly no, especially since general concatenation of buffers is more complicated than appending, for example if source and destination are the same buffer....

While we are on it, we could also unify syntax: instead of writing ``` fn id(x: int32): int32 { return x; } ``` we could write ``` let id: (x:...

Currently, both of these references of `foo` compile to the same code: ``` fn foo(): int32 { return 1; } fn bar() { let x1 = foo(); let x2 =...

Sum types already have all required functionality for switching on enums. The only thing missing is switching on value types. For state machines you should always use named states (enums)...

@32leaves I hope that in Mita the need to express a statemachine using enums and switch (still far better than integer and switch) will be minimal. Ideally users never have...