mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 19:25:56 +03:00
[GH-ISSUE #1002] Resolver & Proto seem to depend unnecessarily on futures-executor #588
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#588
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @antonylsg on GitHub (Jan 29, 2020).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1002
Hello,
It's my first issue. I hope to do it right.
It seems that Resolver and Proto depend on
futures-executorbut do not use it. So why not removing it from their dependency graph?futures0.3 uses["std", "async-await", "executor"]as default features, so we could replace:for both (Resolver and Proto) by:
It should slightly improve the compilation time.
@bluejekyll commented on GitHub (Jan 29, 2020):
I think this was being used in tests at one point, but that may have change. If you’d like to submit a PR, and it passes CI then that would be enough of a test to prove that it’s no longer used there.
Thanks for the issue!