I believe after the fix from #1722, an exception is thrown on every call to AbstractTensor.create.
It gets caught, and it looks like it is the behavior of PointerScope.attach, however the exception-based flow control adds overhead if this is called in a hot path, so perhaps it could be avoided or reworked.
I believe after the fix from #1722, an exception is thrown on every call to
AbstractTensor.create.It gets caught, and it looks like it is the behavior of
PointerScope.attach, however the exception-based flow control adds overhead if this is called in a hot path, so perhaps it could be avoided or reworked.