Page MenuHomeFreeBSD

cdefs(9): encourage __nodiscard over __result_use_check
ClosedPublic

Authored by brooks on Jun 26 2026, 12:16 PM.
Tags
None
Referenced Files
F170970811: D57881.diff
Mon, Sep 7, 10:41 PM
Unknown Object (File)
Sun, Sep 6, 8:26 PM
Unknown Object (File)
Sat, Sep 5, 10:53 PM
Unknown Object (File)
Sat, Sep 5, 8:07 PM
Unknown Object (File)
Sat, Sep 5, 4:01 AM
Unknown Object (File)
Sat, Sep 5, 2:11 AM
Unknown Object (File)
Sat, Sep 5, 12:26 AM
Unknown Object (File)
Fri, Sep 4, 6:36 AM
Subscribers

Details

Summary

nodiscard is closer to (and sometimes expands to) nodiscard from
C23 and C++17 so prefer it to the homegrown
result_use_check.

When nodiscard does expand to nodiscard it must appear entierly
before the function declaration (or between the function name
and argument list) so relocate as appropriate. This differs from
attribute((warn_unused_result)) used by result_use_check which
is more flexible.

Sponsored by: DARPA, AFRL

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable