Is it possible to force the use of “using” for disposable classes?

by

The fact that you need to ensure that the object is disposed indicates a design flaw. It’s fine if disposing is the polite or efficient thing to do, but it should not be semantically necessary.

There is no way to enforce that an object is disposed of via the using statement. However, what you can do is maintain a flag in the object that indicates whether the object was disposed or not, and then write a finalizer that checks that flag. If the finalizer detects that the object wasn’t disposed, then you can have the finalizer, say, terminate the process via failfast. That is, so severely punish the user who neglected to dispose the object that they are forced to either fix their bug or stop using your object.

That doesn’t strike me as nice, good, or polite, but you’re the only one who knows what the terrible, terrible consequences are of failing to dispose the object. Whether applying a punishment to people who fail to follow your crazy rules is better than living with the consequences of them failing to follow the rules is for you to decide.

More Related Contents:

  1. Do HttpClient and HttpClientHandler have to be disposed between requests?
  2. Using statement vs. IDisposable.Dispose()
  3. Dispose, when is it called?
  4. returning in the middle of a using block
  5. What happens if i return before the end of using statement? Will the dispose be called?
  6. yield return statement inside a using() { } block Disposes before executing
  7. Questions about Entity Framework Context Lifetime
  8. What is IDisposable for?
  9. Manually destroy C# objects
  10. using statement FileStream and / or StreamReader – Visual Studio 2012 Warnings
  11. Do I need to Dispose a SemaphoreSlim?
  12. Who Disposes of an IDisposable public property?
  13. Determining if IDisposable should extend an interface or be implemented on a class implementing said interface
  14. Object dispose in IDisposable class
  15. Do you need to dispose of objects and set them to null?
  16. Is there any way to close a StreamWriter without closing its BaseStream?
  17. How do you reconcile IDisposable and IoC?
  18. Does Stream.Dispose always call Stream.Close (and Stream.Flush)
  19. Proper way to dispose a new Form
  20. Right way to dispose Image/Bitmap and PictureBox
  21. Difference between destructor, dispose and finalize method
  22. Implementing IDisposable on a subclass when the parent also implements IDisposable
  23. What does Process.Dispose() actually do?
  24. When should I use GC.SuppressFinalize()?
  25. Who should call Dispose on IDisposable objects when passed into another object?
  26. Avoid calling Invoke when the control is disposed
  27. Why would a class implement IDisposable explicitly instead of implicitly?
  28. Will a using block close a database connection?
  29. What’s the purpose of GC.SuppressFinalize(this) in Dispose() method?
  30. Datatable.Dispose() will make it remove from memory?

Leave a Comment