I was going to wait and see how this is used in container sharing first - is it already going to be called inside of an async function? As far as it being async in web workers, it will be on another thread and we will have to create new async APIs for all of our operations, but they will run synchronously at some point inside of the worker regardless. Lets optionally fix that in the next patch where we use it for container sharing