Joshua Haberman
Joshua Haberman
Yes, to be clear, `toObject()` is _not_ proto3 JSON, it is a pre-existing JSON mapping that does not conform to proto3 JSON.
I suppose the only remaining issue here is that we need to better document that `toObject()` is _not_ proto3 JSON.
No, proto3 JSON is currently not supported with JavaScript. Currently there is not a lot of demand for this inside Google. And whenever we add a feature we have to...
Yes, that would be very welcome. @mprobst suggested to me that we could use http://github.com/angular/clutz to generate TypeScript interfaces from our Closure-annotated source code.
Many of the options we have internally are legacy/deprecated, so we haven't open-sourced them. The ones that we want to keep we will likely want to integrate into `descriptor.proto`. Could...
We don't currently have proto3 JSON support implemented for JavaScript (even internally). Inside Google most JavaScript projects use a wire format called JSPB that is specific to JavaScript and encodes...
> For what it is worth, the JSPB format that you mentioned looks very similar to the goog.proto2 PBLite format from closure-library. Indeed -- that is an example of a...
@stanley-cheung do you have any insight on @pcj's question?
Adding a return value doesn't seem like a breaking change unless it would break existing code somehow. However I have a different concern about making it fluent: consistency. I'm not...
It looks like `-fpermissive` will treat errors like warnings. I don't think we want to do this. What errors are you getting in the mingw build?