I'm going to share some thoughts here simply for discussion purposes - I
don't expect them to be directly applicable.
FWIW, protobuf-net has spoofed inheritance for many many years. I'm able to
do this because protobuf-net only needs to target .NET, which has good
inheritance support.
I don't
I see two problems with this approach. It is neither cut & paste nor
personal preference issue as I see. The real issues I see are:
1) The base message (MSG in the example) and the extended message (MSG2 in
the example ) can belong to different package owned by different group/org.
The
I see two problems with this approach. It is neither cut & paste nor
personal preference issue as I see. The real issues I see are:
1) The base message (MSG in the example) and the extended message (MSG2 in
the example ) can belong to different package owned by different group/org.
The
I see two problems with this approach. It is neither cut & paste nor
personal preference issue as I see. The real issues I see are:
1) The base message (MSG in the example) and the extended message (MSG2 in
the example ) can belong to different package owned by different group/org.
The
