Oscar Campbell

Now we're talking, that's a good suggestion!

> If we have explicit mutable, doesn't that imply we also have implicit immutable? Depends on the context. I have some ideas for "code modes" for the future. You can...

Fragment is now the project term used, thanks for the suggestion! I think we can come up with something even more fitting, but if not, this is _way better_ than...

The "Cigar Walk Syntax" Revisited. ``` onyx list = [1, 2, 3] x = list.map \a\ a + 1 -- explicit args x = list.map \\ _1 + 1 --...

Still need a type-prefix, if local vars, otherwise it's `a(String)`... And `?`/`!` has strong connotations relating to nilable/non-nilable so I don't think it's wise to confuse with mutability/immutability.

Just thinking, all "throws" (well "raise"s) methods use exclamation mark, that's the non-nil connotation I was thinking about. I like the idea of suffixing those concepts though, instead of changing...

The `_1` syntax is the older (compared to `%1`). However, it does not conflict. `_\d` vs `_"."` (simplified). The reason for `\x, y\`: - Compared to `(x, y) ~>`, it's...

I find the `|` much more confusing, thinking of binary operators, while the `\` clearly states that _what follows_ is special. I will keep this in consideration however! The down-side...

> I don't see what exceptions have to do with it. I was referring to stdlib-functions, sorry or the confusion, you raised yet a point to think about though. >...

In the case of just one arg, there's already short-cut notation: - Specifically: `some-fun ~.* 2` - Using auto-params: `some-fun ~> %1 * 2` I don't think one more variant...