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.
Just reading through the MSDN page about new .NET 4.0 feature SpinLock and can not understand idea behind the following statement:
Do not store SpinLock instances in readonly fields.
My feelings that this is somehow related to value-type specifics but not sure how exactly and why. Could anybody bring more light on this point?
The underlying problem is that the C# compiler creates a copy of a
readonlyvalue type field when you call a non-static method on it and executes that method on the copy – because the method could have side effects that change the value of the struct – which is not allowed forreadonlyfields.For further clarification see “Mutating Readonly Structs”.