Skip to content

GILState.Dispose is safe to be called multiple times #1037

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

Merged
merged 2 commits into from
Feb 3, 2020

Conversation

lostmsu
Copy link
Member

@lostmsu lostmsu commented Feb 1, 2020

What does this implement/fix? Explain your changes.

According to IDisposable documentation, Dispose method must be safe to call multiple times.

Checklist

Check all those that are applicable and complete.

  • Make sure to include one or more tests for your change

@codecov-io
Copy link

codecov-io commented Feb 1, 2020

Codecov Report

Merging #1037 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1037   +/-   ##
=======================================
  Coverage   86.71%   86.71%           
=======================================
  Files           1        1           
  Lines         301      301           
=======================================
  Hits          261      261           
  Misses         40       40
Flag Coverage Δ
#setup_linux 65.44% <ø> (ø) ⬆️
#setup_windows 71.42% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b938a5...edfa8f7. Read the comment docs.

@filmor filmor merged commit 3362cf8 into pythonnet:master Feb 3, 2020
@lostmsu lostmsu deleted the PR/NoThrowDispose branch February 27, 2020 21:40
AlexCatarino pushed a commit to QuantConnect/pythonnet that referenced this pull request Jun 27, 2020
* GILState.Dispose is safe to be called multiple times
* test multiple class to GILState.Dispose
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.

3 participants