class WaitForAllBuffersAllocated

Wait until all buffers are allocated.

This FIDL call completes when buffers have been allocated, or completes

with some failure detail if allocation has been attempted but failed.

The following must occur before buffers will be allocated:

* All [`fuchsia.sysmem2/BufferCollectionToken`](s) of the buffer

collection must be turned in via `BindSharedCollection` to get a

[`fuchsia.sysmem2/BufferCollection`] (for brevity, this is assuming

[`fuchsia.sysmem2/BufferCollection.AttachToken`] isn't being used),

or have had [`fuchsia.sysmem2/BufferCollectionToken.Release`] sent

to them.

* All [`fuchsia.sysmem2/BufferCollection`](s) of the buffer collection

must have had [`fuchsia.sysmem2/BufferCollection.SetConstraints`]

sent to them, or had [`fuchsia.sysmem2/BufferCollection.Release`]

sent to them.

- result `buffer_collection_info` The VMO handles and other related

info.

* error `[fuchsia.sysmem2/Error.NO_MEMORY]` The request is valid but

cannot be fulfilled due to resource exhaustion.

* error `[fuchsia.sysmem2/Error.PROTOCOL_DEVIATION`] The request is

malformed.

* error `[fuchsia.sysmem2/Error.CONSTRAINTS_INTERSECTION_EMPTY`] The

request is valid but cannot be satisfied, perhaps due to hardware

limitations. This can happen if participants have incompatible

constraints (empty intersection, roughly speaking). See the log for

more info. In cases where a participant could potentially be treated

as optional, see [`BufferCollectionTokenGroup`]. When using

[`fuchsia.sysmem2/BufferCollection.AttachToken`], this will be the

error code if there aren't enough buffers in the pre-existing

collection to satisfy the constraints set on the attached token and

any sub-tree of tokens derived from the attached token.