[GH-ISSUE #429] Evaluate if ResolverFuture can be Sync #484

Closed
opened 2026-03-15 22:45:17 +03:00 by kerem · 2 comments
Owner

Originally created by @bluejekyll on GitHub (Apr 26, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/429

It's thread safe, it should be Sync. It appears that ResolveError may be making ReslverFuture !Sync.

It's possible this will be helpful: https://github.com/rust-lang-nursery/error-chain/pull/241

Originally created by @bluejekyll on GitHub (Apr 26, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/429 It's thread safe, it should be Sync. It appears that ResolveError may be making ReslverFuture !Sync. It's possible this will be helpful: https://github.com/rust-lang-nursery/error-chain/pull/241
kerem 2026-03-15 22:45:17 +03:00
Author
Owner

@bluejekyll commented on GitHub (May 11, 2018):

Might as well pull this in now: #326

<!-- gh-comment-id:388445200 --> @bluejekyll commented on GitHub (May 11, 2018): Might as well pull this in now: #326
Author
Owner

@hawkw commented on GitHub (May 25, 2018):

There's been an assertion that ResolverFuture is Sync in the ResolverFuture tests since 0bf7909b76, I'm assuming this issue has been resolved?

<!-- gh-comment-id:392204639 --> @hawkw commented on GitHub (May 25, 2018): There's been [an assertion that `ResolverFuture` is `Sync`](https://github.com/bluejekyll/trust-dns/blob/0105b8188a6a2f1f9f03b05772c1eb7c09e68965/resolver/src/resolver_future.rs#L389) in the `ResolverFuture` tests since 0bf7909b76ab2b07a459ece61563a06e9942f3fd, I'm assuming this issue has been resolved?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#484
No description provided.