Out parameter is literally just a workaround for the lack of MRV, the callee still controls the allocation.
For instance `pthread_create` uses an out parameter:
pthread_t threadId;
int err = pthread_create(&threadId, NULL, &threadFunc, NULL);
the first parameter is uninitialised memory, it's only written to by the function. If C had tuples / MRV you'd say (int err, pthread_t threadId) = pthread_create(NULL, &threadFunc, NULL);
instead.But might still use a "destination passing" function, because the point of destination-passing is to make the caller control the allocation, and allow amortisation. "Destination passing" is pretty common in low-ish level Rust APIs for instance, while "out" parameters is largely forbidden (you'd need a function taking a reference to a MaybeUninit or such nonsense).