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
Refactor Secret and ProtectedMemorySecret Dispose usage to avoid requiring implementing classes from having to suppress the finalizer. Refer to https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-dispose.
Secret
ProtectedMemorySecret
Dispose
Abstract class should end up looking like:
protected abstract void Dispose(bool disposing); public void Dispose() { this.Dispose(true); GC.SuppressFinalize(this); }
Will need to test if the new allocator instance is needed as in the current implementation.
The text was updated successfully, but these errors were encountered:
Fix dispose pattern mentioned in Issue #7
ae6908c
This is fixed in my pull request #300
Sorry, something went wrong.
a0be133
c3ca713
No branches or pull requests
Refactor
Secret
andProtectedMemorySecret
Dispose
usage to avoid requiring implementing classes from having to suppress the finalizer. Refer to https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-dispose.Abstract class should end up looking like:
Will need to test if the new allocator instance is needed as in the current implementation.
The text was updated successfully, but these errors were encountered: