Nikodemus Siivola

``` import foo -- import bar import quux ``` ===> ``` import foo -- import bar import quux ```

Currently "module vs name imports" are identified by last element of the import being uppercase or not, which is a leftover from "all globals start with uppercase", which is no...

Add "own method" for interfaces: meaning not inherited, only on the interface object being defined. Own methods cannot be required. eg: ``` -- Object default --> False -- Number default...

Replace `return x` with `x!` -- consistent with using `!` to terminate definitions. Implementation plan: set precedence so that `!` is consumed by sequence parsing, and wraps the prefix in...

Let's try it this way. Might turn out to be a bad idea, but less special cases in syntax seems appealing. Depends on #320 to prevent overloading.

``` Database connect: "localhost" | select: "name" from: "customers" | do: { |each| output println: each } ```

``` let [x, y] = coordinate. ``` ``` method try: [x, y] ... ``` Does this use `at:` to do the destructuring? What about excess elements? How about association syntax?...

Alternatively I could take the Ruby route and allow methods like this: ``` method [key] ... method [key] = value ... ``` The same approch would speak to my question,...

What about `#prefix- sendTo: 1` vs `#- sendTo: 1 with: [2]` Options: 1. `Selector#sendTo:with:` to a sigil with arguments no sends the prefix message. 2. Binary selectors are really "sigil...