promote exception throwing to expression

[jurgenvinju]

Having to write this is awkward:

data MyGraph(MyLayoutStrategy strategy = MyLayoutStrategy () { throw "no default value"; }());

if we promote the throw statement to expression level:

data MyGraph(MyLayoutStrategy strategy = throw "no default value"); 

[DavyLandman]

👍

Can we als do this for other result generating statements? Such as a for?

[DavyLandman]

Ow wait, I thought this was about the shorthand for functions that return one statement..

[mahills]

Instead of making throw an expression, maybe it would make more sense to allow statements on the right-hand side of variable and keyword declarations? This is already allowed for assignables, so this would just make the two more consistent, which seems like a smaller change (given all the assignments currently are of the form <Expression e>;, this also wouldn't require changing any existing code). This would mean that there would be more cases where something is given on the right that doesn't make sense, but, again, we already handle this for assignables.

[jurgenvinju]

@mahills that would also be a good solution, and for single expression function declarations as well. While we haven't integrated expressions and statements yet, it seems like the best thing to do.