Closed bmyates closed 1 year ago
Lifetime management interfaces of USM pools do not match other unified runtime objects.
USM pools use Create/Destroy. All other objects use Create/Retain/Release.
I think for API consistency USM pools should also use Create/Retain/Release.
Additionally, urUSMPoolDestroy requires a ur_context_handle_t input which seems unnecessary. The ur_usm_pool_handle_t alone is enough to uniquely identify the pool to destroy.
urUSMPoolDestroy
ur_context_handle_t
ur_usm_pool_handle_t
Lifetime management interfaces of USM pools do not match other unified runtime objects.
USM pools use Create/Destroy. All other objects use Create/Retain/Release.
I think for API consistency USM pools should also use Create/Retain/Release.