This likely should have been the default from the start, as without it is way to
common to get symbol collisions between different proto files. It would be nice
to support a "migration" mode where both names are created to aid it moving code
to this model, but with ObjC `@class` decls being very common to avoid header
imports to control rebuilds/etc., it doesn't work as an `@class` usage will
error if one also uses `@compatibility_alias`. Falling back to `#define` the two
together also doesn't work as the header with the `@class` will cause methods to
get defined with one interface, but when methods taking those types are define
will likely #import the generate header and thus get the define and end up with
a different signature. So for now, there is no migration support and code has to
be updated in one shot with enable the new prefixing.
- Add a generation option to enable this change in generation.
- Add a second generation option to provide a list of proto package that are
exceptions from using the proto package. This allows easier
migration/updating of code one package at a time.
Adds an option to protoc `--objc_opt=elide_message_metadata` to remove all the property
metadata from message classes. This significantly reduces the codegen size of the clases.
The downside is that iterating through properties using objective c runtime calls will no
longer function. This is mitigated by the fact that most (all?) of the information that
folks are interested in can be extracted via the message descriptor.
We do this by defining our own classes using the `GPB_MESSAGE_SUBCLASS_IMPL` macro.
CreateCodedInput is created from the underlying array behind the ByteString.
If this was created from a larger array (via Memory<byte> or ArrayPool etc)
then the CodedInput refers to the wrong section of memory.
Change is to add the offset and count like the other methods that use the
ArraySegment (ToString, ToBase64, WriteTo).
* Make StringPiece constructible from std::string_view
This improves interop with certain string-like data structures, allowing to save extra allocation.
* Check feature-testing macro before use
This fixes a few kinds of warnings:
- inconsistent-missing-override when the overriding site is missing the
override keyword
- unused-function when a function is neither visible nor used
- unused-private-field when a private field exists but is never used
- sign-compare when unsigned ints are compared to signed ints. Not all
of those have been addressed, but this warning isn't enabled by
default.
This fixes#8612.
Adam Cozzette
Derek Perez
Marcel Lanz
Arthur O'Dwyer
deannagarcia
Ilya Konstantinov
Deanna Garcia
Dave MacLachlan
Thomas Van Lenten
Jie Luo
Jan Tattermusch
Jan Tattermusch
Mark Young
Matt Fowles Kulukundis
Kristofer Spinka
Paul Yang
Marc Plano-Lesay
Yuriy Chernyshov
Stanislav Kashirin
Marc Plano-Lesay