rust-lang / rust-lang/libc

libresolv

Open
#4,611 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

C-API-request
Dominant language
Rust
Stars
2.6k
Forks
1.3k
Avg merge
1d 22h
Merged PRs (30d)
69

Description

resolv.h exposes facilities to resolve DNS records. See:

I would like to understand whether there is a particular reason why the symbols in resolv.h are not covered by the libc crate. If there is no particular reason, I would like to start working on inclusion. My original motivation is to resolve DNS records (of type SRV, TXT) and realized that the Rust standard library does not support this. My next natural step was to check the libc crate.

Target Triples: *-unknown-linux-gnu, *-unknown-android, *-unknown-freebsd (* to be narrowed down by testing).

References:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the symbols and platform differences in resolv.h from Bionic, glibc, musl, and FreeBSD. Check the libc crate's existing platform bindings and test coverage for *-unknown-linux-gnu, *-unknown-android, and *-unknown-freebsd; done means determining supported target triples and covering the relevant libresolv APIs.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, rust
Domain
networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.