[GH-ISSUE #2044] read_system_conf returns different Error types on unix vs windows #859

New issue

Closed

opened 2026-03-16 00:37:00 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 00:37:00 +03:00

Owner

Originally created by @seanmonstar on GitHub (Oct 3, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2044

Describe the bug
On Windows, read_system_conf() has the return type ResolveResult<(ResolverConfig, ResolverOpts)>, whereas on Unix, it has the return type of io::Result<(ResolverConfig, ResolverOpts)>.

Is this intentional? If so, should users expect to use #[cfg] to handle the difference in types?

Version:
Crate: resolver
Version: 0.23.0

Additional context
Noticed here: https://github.com/seanmonstar/reqwest/issues/1991

Originally created by @seanmonstar on GitHub (Oct 3, 2023). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2044 **Describe the bug** On Windows, `read_system_conf()` has the return type `ResolveResult<(ResolverConfig, ResolverOpts)>`, whereas on Unix, it has the return type of `io::Result<(ResolverConfig, ResolverOpts)>`. Is this intentional? If so, should users expect to use `#[cfg]` to handle the difference in types? **Version:** Crate: resolver Version: 0.23.0 **Additional context** Noticed here: https://github.com/seanmonstar/reqwest/issues/1991