Proto3 Nested Message Getter is not useful about protobuf HOT 4 CLOSED

The point is so that deeply nested proto types (e.g. message field in a message that's a field of another message, etc.) can be traversed simply, and without regard for nil message pointers along the way. You can write m.GetFoo().GetBar().GetBaz() and only check for nil right at the end.

If you don't find it useful, don't use it.

from protobuf.

Oh, didn't know you could do m.GetFoo().GetBar().GetBaz().

That's pretty cool. However, it doesn't strike me as immediately obvious. Is there a place where such things are documented? Like golang/protobuf Tips&Tricks? ;)

from protobuf.

It's mentioned in the README and in the package doc, perhaps not so explicitly.

from protobuf.

Is there a reason why the getters don't follow a similar pattern to the C++ API, which allows you to call mutable_field() and creates an object if it doesn't already exist.

Otherwise I end up writing a block like this every time I access a sub message field:

if msg.Field == nil {
  msg.Field = &pb.FieldMsg{}
}

from protobuf.