Skip to content
New issue

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

driver: Don't waste resources setting/being-notified up in progress handler if context cannot be canceled #13

Merged
merged 1 commit into from
Feb 18, 2018

Conversation

navytux
Copy link

@navytux navytux commented Feb 18, 2018

Please see mattn/go-sqlite3#530 for similar
change. Here it is not additional goroutine but a callback setup which
will be called ever 100 ops. We can avoid that if we know that ctx
cannot be canceled.

…andler if context cannot be canceled

Please see mattn/go-sqlite3#530 for similar
change. Here it is not additional goroutine but a callback setup which
will be called ever 100 ops. We can avoid that if we know that ctx
cannot be canceled.
@gwenn
Copy link
Owner

gwenn commented Feb 18, 2018

Thanks.

@gwenn gwenn merged commit 3415a54 into gwenn:master Feb 18, 2018
@navytux
Copy link
Author

navytux commented Feb 18, 2018

You are welcome. And thanks for merging.

@navytux navytux deleted the y/ctx-nocancel branch February 18, 2018 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants