You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discussed this with @lthibault on matrix: It is unintuitive, awkward, and I think even undocumented that the ReleaseFuncs returned by method calls will actually block until the method call returns. Instead, I think they should never block and if a method has not already returned, arrange for the promise to be released when it does return, but don't wait for it.
The trivial implementation of this would be to just fork a goroutine in the body.
The text was updated successfully, but these errors were encountered:
I discussed this with @lthibault on matrix: It is unintuitive, awkward, and I think even undocumented that the
ReleaseFunc
s returned by method calls will actually block until the method call returns. Instead, I think they should never block and if a method has not already returned, arrange for the promise to be released when it does return, but don't wait for it.The trivial implementation of this would be to just fork a goroutine in the body.
The text was updated successfully, but these errors were encountered: