2 ms·
That's not very scalable. Putting more logic in a macro means the compiler needs to reprocess it each time the file is touched, even when the part that's change
by kccqzy 7y ago
That's not very scalable. Putting more logic in a macro means the compiler needs to reprocess it each time the file is touched, even when the part that's changed is not the protos. A separate code gen step means the proto compiler doesn't need to be invoked as often, and the generated files don't need to be recompiled either.
> Will anything downstream match the ".proto" of an object that's missing a bunch of required fields?
You may have missed it, but in proto3, required fields have been removed. All fields are optional now. https://stackoverflow.com/a/31814967/1102119 https://stackoverflow.com/a/31814967/1102119 TL;DR: it's a code evolution problem.
- AaronFriel 7y agoThat doesn't sound right, I don't think there's any reason a proc macro couldn't cache the .proto file's generated code and use the cache between runs.