System.Windows.Point declaration omits IEquatable<Point> - by Glenn Slayden

Status : 


Sign in
to vote
ID 808179 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/9/2013 1:55:01 PM
Access Restriction Public


Even though System.Windows.Point does contain the strongly-typed function...

        public bool Equals(Point value)
            return Equals(this, value);

...this overload will normally not be called (i.e. by EqualityComparer<Point>.Default), because the Point structure does not mention IEquatable<Point> in its declaration.

Instead, the non-strongly-typed Equals(Object) overload is called. It seems to me that this will have a constant performance penalty of boxing the value-typed argument every time.
Sign in to post a comment.
Posted by Chipalo [MSFT] on 11/12/2013 at 4:13 PM
The WPF team has recently reviewed this issue and will not be addressing this issue as at this time the team is focusing on the bugs impacting the highest number of WPF developers. If you believe that this was resolved in error, please reactivate this bug with any necessary supporting details.

We appreciate the feedback. However, this issue will not be addressed in the next version of WPF. Thank you.
–WPF Team.
Posted by Macy [MSFT] on 11/10/2013 at 7:25 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Macy [MSFT] on 11/9/2013 at 2:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(