for messages.proto.
If we kill the internal namespace altogether, it would make it
much
easier to expose some headers as public headers for
modularization,
etc..
This will also help us get rid of namespace internal from some
of
the
public headers that we already have
and the effects on
upgrades, etc., if we change the namespace/package for these
protobufs.
If
this turns out to be a real concern, we can possibly keep the
internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier
for messages.proto.
If we kill the internal namespace altogether, it would make it
much
easier to expose some headers as public headers for modularization,
etc..
This will also help us get rid of namespace internal from some of
the
public headers that we already have
/package for these
protobufs. If
this turns out to be a real concern, we can possibly keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization,
etc
the
internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it
much
easier to expose some headers as public headers for modularization,
etc..
This will also help us get rid of namespace internal from some of
the
public
to be a real concern, we can possibly keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization, etc..
This will also help us get rid of namespace internal from some
possibly keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization,
etc..
This will also help us get rid of namespace internal from some of the
public headers
keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization,
etc..
This will also help us get rid of namespace internal from some of the
public headers that we
for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization, etc..
This will also help us get rid of namespace internal from some of the
public headers that we already have.
The motivation
for these protobufs. If
this turns out to be a real concern, we can possibly keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization, etc..
This will also help us get rid
keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization, etc..
This will also help us get rid of namespace internal from some of the
public headers that we
.
One possible concern here might be messages.proto and the effects on
upgrades, etc., if we change the namespace/package for these protobufs. If
this turns out to be a real concern, we can possibly keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether
be messages.proto and the effects on
upgrades, etc., if we change the namespace/package for these protobufs.
If
this turns out to be a real concern, we can possibly keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier
and the effects on
upgrades, etc., if we change the namespace/package for these
protobufs. If
this turns out to be a real concern, we can possibly keep the internal
namespace for messages.proto.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers
I want to note that if there was any change in behavior around this change
that would likely indicate a serious compiler bug. Namespaces are something
that is purely programmer visible in C++, the symbol names will change
slightly for things that were internal, but nothing else. Things need to be
.
If we kill the internal namespace altogether, it would make it much
easier to expose some headers as public headers for modularization,
etc..
This will also help us get rid of namespace internal from some of the
public headers that we already have.
The motivation for killing
16 matches
Mail list logo