I prefer this syntax because, to me, it's easier to parse and it's closer to how ( and ) are treated.

In the case of inline blocks, the { and } characters actually act a lot like ( and ) because the latter isn't even allowed.
Bring back alternate example. Make optionalness explicit rather than implict
Merge pull request #3 from outright/curly-braces

Curly braces