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
Unknown Object (File)
Thu, Aug 13, 10:51 AM
Unknown Object (File)
Thu, Aug 13, 12:46 AM
Unknown Object (File)
Wed, Aug 12, 8:52 PM
Unknown Object (File)
Tue, Aug 11, 6:47 PM
Unknown Object (File)
Tue, Aug 11, 11:23 AM
Unknown Object (File)
Mon, Aug 10, 11:13 AM
Unknown Object (File)
Mon, Aug 10, 10:04 AM
Unknown Object (File)
Sun, Aug 9, 5:28 PM
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