[Mono-bugs] [Bug 82087][Nor] Changed - Problem in Hashtable when using custom IComparer

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by lluis at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=82087

--- shadow/82087	2007-07-12 13:55:56.000000000 -0400
+++ shadow/82087.tmp.7776	2007-07-16 11:33:04.000000000 -0400
@@ -1,23 +1,23 @@
 Bug#: 82087
 Product: Mono: Class Libraries
 Version: 1.2
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: lluis at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Problem in Hastable when using custom IComparer
+Summary: Problem in Hashtable when using custom IComparer
 
 Hashtable has a problem that may manifest when using a custom IComparer.
 The problem is that in some cases Hastable may call IComparer.Compare
 (object x, object y), providing an object in x or y which may not be of the
 type expected by the comparer. That's because Hashtable internally uses a
 special key marker object for slots which have been deleted, and doesn't do