Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Docs build with warnings

Aperta
#1,685 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
74/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

Run RUSTDOCFLAGS="-D warnings" cargo doc --no-deps --features all-apis to reproduce the failures. Inspect the unresolved references in src/backend/libc/process/types.rs, src/fs/fd.rs, src/io/dup.rs, src/mm/mmap.rs, src/net/send_recv/mod.rs, src/net/socket.rs, src/pipe.rs, and src/process/rlimit.rs. Done means the documentation build completes without unresolved-link warnings.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

$ RUSTDOCFLAGS="-D warnings" cargo doc --no-deps --features all-apis
error: unresolved link to `crate::process::prlimit`
  --> src/backend/libc/process/types.rs:16:18
   |
16 | /// [`prlimit`]: crate::process::prlimit
   |                  ^^^^^^^^^^^^^^^^^^^^^^^ no item named `prlimit` in module `process`
   |
   = note: `-D rustdoc::broken-intra-doc-links` implied by `-D warnings`
   = help: to override `-D warnings` add `#[allow(rustdoc::broken_intra_doc_links)]`

error: unresolved link to `crate::fs::OFlags::PATH`
   --> src/fs/fd.rs:121:23
    |
121 | /// [`OFlags::PATH`]: crate::fs::OFlags::PATH
    |                       ^^^^^^^^^^^^^^^^^^^^^^^ the struct `OFlags` has no field or associated item named `PATH`

error: unresolved link to `DupFlags::CLOEXEC`
  --> src/io/dup.rs:56:42
   |
56 | /// set `O_CLOEXEC`, use [`dup3`] with [`DupFlags::CLOEXEC`] on platforms which
   |                                          ^^^^^^^^^^^^^^^^^ the struct `DupFlags` has no field or associated item named `CLOEXEC`

error: unresolved link to `mlock_with`
   --> src/mm/mmap.rs:283:11
    |
283 | /// See [`mlock_with`] to pass additional flags.
    |           ^^^^^^^^^^ no item named `mlock_with` in scope
    |
    = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`

error: unresolved link to `RecvFlags::TRUNC`
  --> src/net/send_recv/mod.rs:34:7
   |
34 | /// [`RecvFlags::TRUNC`] flag.
   |       ^^^^^^^^^^^^^^^^ the struct `RecvFlags` has no field or associated item named `TRUNC`

error: unresolved link to `RecvFlags::TRUNC`
   --> src/net/send_recv/mod.rs:113:7
    |
113 | /// [`RecvFlags::TRUNC`] flag.
    |       ^^^^^^^^^^^^^^^^ the struct `RecvFlags` has no field or associated item named `TRUNC`

error: unresolved link to `SocketFlags::CLOEXEC`
  --> src/net/socket.rs:17:35
   |
17 | /// To pass extra flags such as [`SocketFlags::CLOEXEC`] or
   |                                   ^^^^^^^^^^^^^^^^^^^^ the struct `SocketFlags` has no field or associated item named `CLOEXEC`

error: unresolved link to `SocketFlags::NONBLOCK`
  --> src/net/socket.rs:18:7
   |
18 | /// [`SocketFlags::NONBLOCK`], use [`socket_with`].
   |       ^^^^^^^^^^^^^^^^^^^^^ the struct `SocketFlags` has no field or associated item named `NONBLOCK`

error: unresolved link to `pipe_with`
  --> src/pipe.rs:53:11
   |
53 | /// See [`pipe_with`] to pass additional flags.
   |           ^^^^^^^^^ no item named `pipe_with` in scope
   |
   = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`

error: unresolved link to `prlimit`
 --> src/process/rlimit.rs:8:26
  |
8 | /// [`setrlimit`], and [`prlimit`].
  |                          ^^^^^^^ no item named `prlimit` in scope
  |
  = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`

error: could not document `rustix`
Lingua principale
Rust
Stelle
2.1k
Fork
298
Merge medio
9g 3h
PR unite (30g)
3

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bytecodealliance/rustix

Tutte le issue di bytecodealliance/rustix

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.