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.

Sign up for GitHub

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

Jump to bottom

Make backtrace dependency optional #5875

Open
DemiMarie opened this issue Jul 17, 2023 · 1 comment
Open

Make backtrace dependency optional #5875

DemiMarie opened this issue Jul 17, 2023 · 1 comment
Labels
A-tokio Area: The main tokio crate C-feature-request Category: A feature request. M-taskdump --cfg tokio_taskdump

Comments

@DemiMarie
Copy link

Is your feature request related to a problem? Please describe.
The backtrace dependency pulls in several other crates, such as miniz_oxide.

Describe the solution you'd like
Make the backtrace dependency optional.

Describe alternatives you've considered
None

Additional context
backtrace pulls in several additional dependencies, including miniz_oxide.
@DemiMarie DemiMarie added A-tokio Area: The main tokio crate C-feature-request Category: A feature request. labels Jul 17, 2023
@Darksonn
Copy link
Contributor

The backtrace dependency should not get pulled in unless you've specified --cfg tokio_taskdump.

@Darksonn Darksonn added the M-taskdump --cfg tokio_taskdump label Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-tokio Area: The main tokio crate C-feature-request Category: A feature request. M-taskdump --cfg tokio_taskdump
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Darksonn @DemiMarie