You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the python lwpb code can't resolve nested definitions like this:
message A {
message B {
enum C {
...
};
};
};
message D {
optional A.B.C stuff = 1;
};
The rules for resolving type names follow C++ scoping.
This feels like an unnecessary complication in the protocol buffers spec -- I've personally never had a need for it and simply use a flat list of definitions in my .proto files.
However, it's in the spec, so see if it can be implemented in the descriptor code.
The text was updated successfully, but these errors were encountered:
Currently, the python lwpb code can't resolve nested definitions like this:
The rules for resolving type names follow C++ scoping.
This feels like an unnecessary complication in the protocol buffers spec -- I've personally never had a need for it and simply use a flat list of definitions in my .proto files.
However, it's in the spec, so see if it can be implemented in the descriptor code.
The text was updated successfully, but these errors were encountered: