Hahahaha, this is what we needed: a programming language with unmatched braces because the opening brace can be inferred from context... Well, no surprise that this is coming from the Vim creator.
So it might look silly, but there is no deep reason it couldn't have just been
int main()
printf("hello");
}
int foo(x)
int x;
{
return x;
}
int foo(int x) [[gnu::aligned]] {
return x;
}That’s a mouth, not a paren :/ I won’t be able to sleep tonight :)) (that’s better
main(): int
printf "hello"
0
let main () =
printf "hello"
0OK, I'll stop now, but the point is: matching braces provide visual structure that's helpful to read code, even if it's syntactically redundant.
One is designed for machines to parse unambiguously, the other has grown organically and chaotically over hundreds of years. Machine parsing has never been a design concern.
Oberon:
IF a < b THEN
...
END
IF a < b THEN
BEGIN
...
END