Skip to content

Conversation

@daxpedda
Copy link
Contributor

@daxpedda daxpedda commented Jun 9, 2022

Fixes: #2157

Motivation

My main motivation was to improve the user-experience by returning a more concrete error type without a Box around it, which makes it more compatible with other error types, like anyhow::Result.

Solution

The solution is simple, just change the error type. I'm assuming that this PR is still a problem, because it might count as a breaking change?

@daxpedda daxpedda requested review from a team, davidbarsky and hawkw as code owners June 9, 2022 12:58
@bryangarza bryangarza added this to the tracing-subscriber 0.4 milestone Jun 9, 2022
@bryangarza bryangarza self-requested a review June 9, 2022 19:06
@bryangarza
Copy link
Member

Seems fine to me, I think we'll have to wait to merge until we're ready to release tracing-subscriber 0.4 though (I assigned the relevant Milestone for now)

@hawkw
Copy link
Member

hawkw commented Jun 9, 2022

Yeah, I'm fine with adding a named error type, but this will require waiting for tracing-subscriber 0.4.

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.

tracing-subscriber: fmt::try_init error type

3 participants