do not implement IDisposable

Dequeue operations are permitted (and in many cases very much
necessary) after Close() until the queue is drained. Since Dispose()
calls Close() (and what else would it do?), we would be left with an
object that has been disposed but must still be useable. While there
is nothing technically stopping that from happening, it constitutes a
departure from the intent of IDisposable.

Author: Matthias Radestock

src/util/SharedQueue.cs

@@ -61,7 +61,7 @@
 
 namespace RabbitMQ.Util {
     ///<summary>A thread-safe shared queue implementation.</summary>
-    public class SharedQueue: IDisposable {
+    public class SharedQueue {
         ///<summary>The shared queue.</summary>
         ///<remarks>
         ///Subclasses must ensure appropriate locking discipline when
@@ -88,12 +88,6 @@ public void Close() {
             }
         }
 
-        ///<summary>Implement IDisposable.Dispose. Delegates directly
-        ///to Close().</summary>
-        public void Dispose() {
-            Close();
-        }
-
         ///<summary>Call only when the lock on m_queue is held.</summary>
         /// <exception cref="EndOfStreamException" />
         private void EnsureIsOpen() {