Oscar Campbell

Thanks for pointing it out, it's also not consistent with funcs/methods. But there are also lambdas and functors which has the same behaviour as Type. It's a value primarily. [ed:...

After a quick smoke-break, my brain tells me it's better to improve error-messages if `SomeType` is used in a context where it reasonably should have been `SomeType()`, "error so and...

Further on the issue at hand: I've also been thinking about whether operators should be enclosed with delimiters in function-defs for clarity: **Now** ``` onyx ext I32 *(x SomeType) ->...

I want to either implement or dismiss the syntax change suggest in https://github.com/ozra/onyx-lang/issues/11#issuecomment-217818212, so that this basic construct of the language is finally settled and nailed down. I think it...

> fn5 (x Int) -> x*x should not throw an error. Correct! That's business as usual. Only when the arrow is followed immediately by what fits the rules of a...

Damn, I've been struck with the Flu from Hell, quick comment before bed again: Handling bool's differently from all other types in this construct will lead to nothing good. Just...

In response to request for improved pattern matcher in other issue: Yes, a real pattern matching `match`-construct should definitely be implemented in Onyx. It should go into a separate issue...

Would be nice to clean this up in the code base and settle on definite keywords. The alternative syntaxes for branches will still be available (indented, prefixed with `|`, prefixed...

The reasoning was simply that the behave differently, so different keywords. `branch` is just a cleaner way of writing multiple `if .. elif .. else` branches, while `switch` does an...

There's no technical problem using the same keyword, so only what's best for the lang should be considered. What's the reasoning for preferring one keyword?