not sure if this was discussed somewhere before, but what about:
func foo() throws<FooError>
// instead of
func foo() throws(FooError)
at least at first glance it feels more type-related and less function-y to me...
1 Like