I was also looking for typedef in .proto and landed here.
Seems like an obvious feature to have.
On Wednesday, January 18, 2017 at 9:09:00 PM UTC-8, Arpit Baldeva wrote:
>
> Hi Adam,
>
> Thanks for the response. I agree that any change should be scrutinized and
> evaluated very carefully.
>
> I
Hi Adam,
Thanks for the response. I agree that any change should be scrutinized and
evaluated very carefully.
I am somewhat surprised though. May be it has to do with my primary
language background being C++ where typedefs are commonplace. Defining a
new message just to embed a single value will
Arpit, I should just let you know in advance that we tend to be pretty
conservative about making a big change like this and so we would probably
be reluctant to do it unless it has a major positive impact. I'm skeptical
of whether this feature adds enough value, because most of the time I think
dev
Should I file a GitHub issue for this? I am not sure what the right
protocol is.
Thanks.
On Wednesday, November 23, 2016 at 1:04:07 PM UTC-8, Arpit Baldeva wrote:
>
> Thanks for the info. Typedef support would be pretty much useful for
> regular use cases in C/C++ languages. For example, if w
Thanks for the info. Typedef support would be pretty much useful for
regular use cases in C/C++ languages. For example, if we have 100 messages
that each have a game id, it'd be nice to just typedef say a uint64 to
GameId rather than using it explicitly in each place. This avoids errors
like someon
I don't think we have any specific plans to do this, but we could consider
doing at some point if it would be useful. Do you have a particular use
case that would benefit from support for type aliasing?
On Mon, Nov 21, 2016 at 4:13 PM, Arpit Baldeva wrote:
> Hi,
>
> Are there any plans to introd
