NNG_AIO_SET_INPUT(3)

📦
version 1.12.0 · 4 versions
, in ubuntu stonking

💖 NNG_AIO_SET_INPUT(3) 💖

okay bestie, so this is a page from the NNG Reference Manual and it's literally all about nng_aio_set_input — the glow-up your async operation's input params deserve ✨

✨ NAME ✨

nng_aio_set_input — set input parameter 🎀

🌸 SYNOPSIS 🌸

#include <nng/nng.h>

void nng_aio_set_input(nng_aio *aio, unsigned int index, void *param);

🦋 DESCRIPTION 🦋

So the nng_aio_set_input() function sets the input parameter at index to param for the asynchronous operation that's associated with aio. Basically you're handing your op its lil snack before it goes off and does its thing 🍓

The type and semantics of input parameters are decided by the specific operations themselves — so the caller has to supply inputs that actually make sense for the operation being performed. No vibes-based guessing, bestie, the op knows what it wants.

The valid values of index range from zero (0) to three (3), because no operation currently defined can accept more than four parameters. (And yeah, this limit could totally increase in the future 👀)

Note 📝 If the index doesn't correspond to a defined input for the operation, then this function will just have no effect. Nothing. Nada. It's giving "sent to the void".
Important 🚨 It is an error to call this function while the aio is currently in use by an active asynchronous operation. Do not do this. Not me catching you trying to do this 💀

An input parameter set with this function may be retrieved later with the nng_aio_get_input() function — so you can always check back on it, iconic behaviour 🫶

💅 RETURN VALUES 💅

None. Nothing. Zero. Nil. The void returns nothing because it doesn't have to 😌

🙈 ERRORS 🙈

None. It's not the throwing type, it just quietly does its thing ✨

🔥 SEE ALSO 🔥

mwah 💋 this lil page was served up as NNG_AIO_SET_INPUT(3) on 2026-06-30 — go forth and set those inputs, bestie, you got this fr fr 👑🌈

📦 where this page comes from