QB_LOOP_T...E_TIME_GET(3)

πŸ’– qb_loop_timer_expire_time_get β€” a libqb programmer's manual moment πŸ’–

okay bestie, welcome to libqb Programmer's Manual, section 3, page qb_loop_timer_expire_time_get(3). yes that's a long name, we've been over this, it's giving ✨descriptive✨ and we respect it.


🌸 NAME 🌸

qb_loop_timer_expire_time_get β€” get the expiration time of the timer, as set when the timer was created. that's it, that's the whole job, and she does it well πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

#include <qb/qbloop.h>

uint64_t qb_loop_timer_expire_time_get(
    struct qb_loop       *l,   /* pointer to the loop instance */
    qb_loop_timer_handle  th   /* timer handle. */
);

look at that signature. uint64_t return, two args, no drama. iconic behavior fr fr.


πŸ¦‹ PARAMS πŸ¦‹

  • l β€” pointer to the loop instance 🫢
  • th β€” timer handle. (yes with the period, that's just how she is)

✨ DESCRIPTION ✨

bestie. the DESCRIPTION section is literally empty in the original. the author said "the NAME section already ate, we're done here" and honestly? valid. no extra lore, no secret paragraphs. moving on πŸ’€

πŸ”₯ RETURN VALUE πŸ”₯

nano seconds at which the timer will expire ⏰

like, the actual number. in nanoseconds. not seconds, not milliseconds, NANO. slay units, tiny units, very precise queen.


πŸ’œ NOTE πŸ’œ

if the timer has already expired it will return 0

that's the vibe check. expired timer = 0. don't come for me, that's just what she said 🌸


🌈 SEE ALSO 🌈

the whole friend group, in the exact order they were introduced:

ngl that's a lot of besties but every single one of them matters πŸ’–


Copyright (C) 2010-2020 Red Hat, Inc.

periodt.


aaaand that's the page! mwah πŸ’‹ this one came from LIBQB, dated 2025-09-16, and she's still out here answering the same question: when does my timer expire? πŸ’…πŸ¦‹βœ¨

πŸ“¦ where this page comes from