This looks like a bug (I think the warning is spurious and can be ignored); thanks for the repro info. :)

By on 2/26/2009 12:18 PM ()

You are welcome.
I ended up removing the type-specific overload because it was getting ignored by the (=) operator anyway.
Even if I only specified the type-specific method, the (=) operator would then use Object.Equals(obj) from System.Object.
Defining a static member (=) doesn't do it either, I suspect the global (=) is defined in terms of .Equals
So... I guess I could redefine the (=) operator using something like let inline (=) x y = ... but I would be afraid of the implications.

By on 2/26/2009 2:32 PM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper