Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/upgrade go dependencies 2023-12-18 #122

Conversation

stagnation
Copy link

What's really annoying about the latest version of OpenTelemetry is that they've redefined the Span, Tracer and TracerProvider interfaces to contain private methods, so that you no longer have the ability to fully implement them yourself. This is done to provide gradual forward compatibility, but I don't buy it. In my case I want to get explicit build failures, so that I know I need to extend my implementations.

Solve this by explicitly embedding embedded.* into our types. For gomock we now need to declare our very own wrappers. Very annoying.

What's really annoying about the latest version of OpenTelemetry is that
they've redefined the Span, Tracer and TracerProvider interfaces to
contain private methods, so that you no longer have the ability to fully
implement them yourself. This is done to provide gradual forward
compatibility, but I don't buy it. In my case I want to get explicit
build failures, so that I know I need to extend my implementations.

Solve this by explicitly embedding embedded.* into our types. For gomock
we now need to declare our very own wrappers. Very annoying.
@stagnation stagnation force-pushed the feature/upgrade-go-dependencies-2023-12-18 branch from 2a5244d to 9f9ef21 Compare December 18, 2023 12:19
@EdSchouten EdSchouten merged commit 70154e8 into buildbarn:master Dec 20, 2023
1 check passed
@stagnation stagnation deleted the feature/upgrade-go-dependencies-2023-12-18 branch December 20, 2023 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants