To clarify, required extensions are disallowed, required fields in an
extension message is allowed. I.e., the following is ok:
message A {
extensions 1 to max;
}
message B {
extend A { *optional* B extension = 1; }
*required* string s = 1;
}
On Sat, Oct 25, 2014 at 2:19 PM, Feng Xiao <[email protected]> wrote:
> This is working as intended. Extensions, by its definition, is something
> optionally attached to a message and it doesn't make sense for it to be
> required, and technically there is no way to enforce this requirement
> because a binary can be compiled without the extension definition in which
> case there is no way to know whether the extension is required or optional.
>
> And the change in 2.6.0 is actually a bug fix because in previous versions
> the required label is simply ignored and the extension is treated as
> optional any way.
>
>
> On Sat, Oct 25, 2014 at 5:28 AM, Anthony Sampton <
> [email protected]> wrote:
>
>>
>> I'm pretty sure it's not only me who faced with this problem, BUMP.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Protocol Buffers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> Visit this group at http://groups.google.com/group/protobuf.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
