Gerald Sangudi

@twdsilva This pull request now includes a new test using a mini-cluster. Please review, thanks.

Or perhaps underscore as the zero designator. Either would be readable.

``` Foo(default, default, default) Foo({}, {}, {}) Foo(_, _, _) ``` I find the latter two more readable, but `default` or other keyword is also fine with a syntax highlighter....

It's not stated why the previous proposal was closed, and I had not seen it when I searched and filed this proposal. I raised this proposal from direct and repeated...

Per your comment, untyped constants do support type inference, and overloaded nil does support type inference (issue with nil interfaces noted). The net effect of this is that type inference...

By type inference, I mean the omission of the type name in the text of the value. Your example of `a == {}` is interesting. I write these all the...

Const-ness is orthogonal to type inference.

Yes, it's possible to do less. But I haven't seen any argument for why less is more in this case, or any downside to the universal zero.

As a detail, I don't see any ambiguity with `if v == {}` Every binary operator requires expressions on both sides, not statement blocks.

Extending `nil` to all composites would address the convenience issues. However, a universal zero would work for all types, and should have additional benefits for tooling, generics, etc. Also, a...