Ben Ashbaugh

> I wanted to leave some high-level thoughts about how this extension could work.... I think the comment above describes one way this extension could work, but not necessarily the...

For (1) we could modify the error description to cover this scenario if you'd like. I agree `CL_INVALID_PLATFORM` makes the most sense. Maybe something like: > [CL_INVALID_PLATFORM](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#CL_INVALID_PLATFORM) if ~~properties is...

I think this issue was fixed by #1063 so I'm going to close this issue. If anything more is needed please feel free to re-open it or file another issue...

I'll fix this one after #1069 is merged.

I think this is another case to consider, especially for implementations that implement queues lazily (AKA "batched"). I think this would be considered simultaneous use? ```c++ // Case A: queue...

Interesting... I think this implies that all three of the cases above should be considered "simultaneous use", agreed? Basically, to use a command-buffer "non-simultaneously" you need to observe that the...

> What about `clSetEventCallback`? [...] Yes, I think this could work to avoid "simultaneous use" too, because of this line in the spec? "If a callback procedure P is registered...

Noting for completeness: there was also some discussion of a clone API in internal issue 251, in two places actually. I agree this is something we should consider.

Neat! > I'm proposing we resolve all of these util the script reports zero and then make sure it is routinely run as part of the spec generation and CI....

> > All of the CL_HALF_XXX enums could be treated analogous to the CL_FLT_XXX enums, which are currently assigned to core OpenCL 1.0 and listed in cl_platform.h. > > Not...