Jose
Jose
The C# doc comment is different: ``` /// Creates a new proxy that is identical to the passed proxy, except /// for its facet. This call contacts /// the server...
There is a circular dependency at the package level. `IceRpc.BuildTelemetry.Reporter` needs to include the `IceRpc` assemblies and we need `IceRpc.Slice.Tools` to build them. But we also want to distribute `IceRpc.BuildTelemetry.Reporter`...
I think we have to restructure things to: - Build `IceRpc.Slice.Tools` -> `IceRpc` -> `IceRpc.BuildTelemetry.Reporter` IceRpc.Slice.Tools should have no dependencies on the build telemetry - For packaging, repackage `IceRpc.Slice.Tools` to...
How would you deal with Enum/struct parameters that rely on generated code for marshaling?
Similar issue in https://github.com/dotnet/runtime/issues/104737
Would be nice to have a way to configure these limits when using other overloads for decoding data, as opposed to only offering this functionally with the CodedInputStream API.
This is now supported with the new APIs, we will upgrade 3.8 docs with concrete examples.
> Should we first eliminate the Adapters "namespace"? I think we need to do both together, otherwise, you cannot have `DataStorm.Node.Server.Enabled` and use `DataStorm.Node.Server` as the adapter name. I think...
Removed PHP and Ruby because we are not generating doc comments there.
C# was fixed in d062993f3684ab08f87b842f94c4470e2069d7c4