✅ Function argument class reference / clone (best practice(s))
Hello,
I'm a total newbie in
When writing a function what are the best practices to tell the caller (I'm mostly interested with a
- The parameter will be taken (owned by the
- You can use it after since the argument will be cloned (is it a good practice ? is
- The argument will be modified after calling the method / function (is
Does it make sense to
I read the documentation (https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/method-parameters) and it clearly says about reference types (such as
How do you know in which case you are when calling a method / function ? (I hope my questions make sense, I apologize if it doesn't
-> I don't want to modify a value / variable and have unintended impact (same reference) on another variable)
Thank you very much in advance for any help
I'm a total newbie in
C#RustCC++When writing a function what are the best practices to tell the caller (I'm mostly interested with a
class- The parameter will be taken (owned by the
class- You can use it after since the argument will be cloned (is it a good practice ? is
ICloneable- The argument will be modified after calling the method / function (is
refDoes it make sense to
Clone()C#I read the documentation (https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/method-parameters) and it clearly says about reference types (such as
classThe called method can't reassign the instance in the calling method. However, the called method can use the copy of the reference to access the instance members. If the called method changes an instance member, the calling method also sees those changes since it references the same instance.
How do you know in which case you are when calling a method / function ? (I hope my questions make sense, I apologize if it doesn't
-> I don't want to modify a value / variable and have unintended impact (same reference) on another variable)Thank you very much in advance for any help
Parameter modifiers enable pass-by-reference semantics, with distinctions for read-only, and
outparams
