You don't have to worry about the uninterpreted_option field. It's an
internal implementation detail of the parser. You should pretend it isn't
there.
The comment is saying that the uninterpreted_option field must have the name
"uninterpreted_option" in all *Options messages because the parser us
I was just looking over descriptor.proto for the option extensions,
and I spotted this comment that I hadn't seen before:
// Clients may define custom options as extensions of the *Options
messages.
// These extensions may not yet be known at parsing time, so the
parser cannot
// store the values
