We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The restriction is checking if container scope is the same as the current ambient scope from the context, and only then disposing it - otherwise not.
Now I am disposing current ambient scope without any checks - anyway ambient scopes could be changed any time not depending on container.
This may provide more predictability for AsyncExecutionFlowScopeContext and ThreadScopeContext.
AsyncExecutionFlowScopeContext
ThreadScopeContext
The text was updated successfully, but these errors were encountered:
fixed
Sorry, something went wrong.
dadhi
No branches or pull requests
The restriction is checking if container scope is the same as the current ambient scope from the context, and only then disposing it - otherwise not.
Now I am disposing current ambient scope without any checks - anyway ambient scopes could be changed any time not depending on container.
This may provide more predictability for
AsyncExecutionFlowScopeContext
andThreadScopeContext
.The text was updated successfully, but these errors were encountered: