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
IMO, the change here was technically correct (see #7090 (comment)) but impractical for the broader ecosystem. Typically deprecations like this are done in more obscure functions that have relatively small impact; I have never seen (in the Go ecosystem), such an impactful deprecation before.
As #7090 (comment) notes, there are 178,000 usages across the open source ecosystem of these functions. With this change, all of them will need to be updated (if not to NewClient, to silence the linting). This is placing a substantial burden on developers for little benefit to them. Isolating to specific orgs, Kubernetes and Istio both have well over 100 usages of these methods.
I don't feel its required for a function to be formally // Deprecated: (which triggers the linters) to discourage usage. As prior art, in both Go stdlib and gRPC-go itself, DialContext was added to ~replace Dial. In both of these cases, the other was not formally deprecated.
I propose the comment on these functions is tweaked to not trigger linters.
The text was updated successfully, but these errors were encountered:
We're following all the guidelines here as best we can. I'm sorry this has inconvenienced you, but you probably do need a way to allow the use of deprecated features in your presubmits, so you don't have to immediately update >100 call sites at the same time you update a dependency. For example, we have a list of exceptions here:
See #7090.
IMO, the change here was technically correct (see #7090 (comment)) but impractical for the broader ecosystem. Typically deprecations like this are done in more obscure functions that have relatively small impact; I have never seen (in the Go ecosystem), such an impactful deprecation before.
As #7090 (comment) notes, there are 178,000 usages across the open source ecosystem of these functions. With this change, all of them will need to be updated (if not to NewClient, to silence the linting). This is placing a substantial burden on developers for little benefit to them. Isolating to specific orgs, Kubernetes and Istio both have well over 100 usages of these methods.
I don't feel its required for a function to be formally
// Deprecated:
(which triggers the linters) to discourage usage. As prior art, in both Go stdlib and gRPC-go itself, DialContext was added to ~replace Dial. In both of these cases, the other was not formally deprecated.I propose the comment on these functions is tweaked to not trigger linters.
The text was updated successfully, but these errors were encountered: