Jon Skeet
Jon Skeet
When considering the change in C# SDK due to #1050, it strikes me that there's a potential ambiguity about an AMQP message with a mixture of `cloudEvents:` and `cloudEvents_` prefixes....
Currently (in both protoc and the support library, I believe) we use the filename (e.g. "google/protobuf/wrappers.proto") to detect that a proto is a well-known type. We could potentially use the...
As observed via https://stackoverflow.com/questions/63923968, the claim that: > In some cases, unsafe code may increase an application's performance by removing array bounds checks. ... can me read as "it makes...
[AIP-213](https://google.aip.dev/213) states: > APIs should not directly depend on protos defined in other APIs. Instead, they should copy and paste the applicable messages into their own API. When doing so,...
We won't merge this until we've had the go-ahead, but this is just in preparation.
This is currently just a draft of the action from #229 - basically the production code is there, but no tests. I wanted to get some feedback on whether or...
Extensions are inherently somewhat-unstable, as we've seen with [distributed tracing](https://github.com/cloudevents/spec/pull/751) and [sequence](https://github.com/cloudevents/spec/blob/main/cloudevents/extensions/sequence.md). That makes it hard to provide a stable API. Proposal: - Make the existing extensions obsolete (with useful...
(From #230) Various formats (certainly JSON, XML and Protobuf) have a natural container format (e.g. JObject/JsonElement, XElement, the CloudEvent message) and it can be useful to expose conversions for those...
Fixes #10776 - at least for the "main/test" protos. Conformance and compatibility still to be done.
We have a fair amount of generated code in https://github.com/protocolbuffers/protobuf/tree/main/csharp/src It can be useful to differentiate this code based purely on the extension, and .NET typically uses .g.cs as a...