Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I found this in System.Object
[SecuritySafeCritical]
protected object MemberwiseClone();
Why isn’t this virtual? Wouldnt this break if i put myclass into object then call MemberwiseClone? wouldnt it called object.MemberwiseClone() in that case which has no idea about my implementation of MemberwiseClone? (I guess it can cheat with reflection but virtual would do exactly what it needs). I dont understand why is this not virtual? Also note Equals, ToString, etc are (public) virtual.
MemberwiseClone is implemented directly by the CLR, so it knows exactly what type your object is and how to make a memberwise clone. There’s only one way to do it, so there’s no reason to let you “customize” the behavior with some specialized logic, like Equals, ToString, etc. Another way to think about it: if you could override it, what would you do differently than the base implementation that wouldn’t break the contract of the API?