What kind of memory semantics govern array assignment in c#?

Question

Given the following: byte[] sData; and a function declared as private byte[] construct_command()

if I were to then assign the resul

Answer 1

Assuming sData is a local variable, it will live in the stack and it will refer to the array returned by the method. The method does not return the contents of the array itself, but a reference to the array.

In .net, arrays are first class objects and all array-type variables are in fact references.

Answer 2

sData will point to the contents of what's returned from the function. Arrays in C# are reference types, which means that assigning one array from another simply copies the reference rather than allocating new data.

Answer 3

The assignment will simply assign the sData to reference the instance returned by construct_command. No copying of data will occur.

In general, the CLR breaks the world down into 2 types

• Value Types: This is anything that derives from System.ValueType. Assignment between values of these types happens by value and essentially results in a copy of the values between locations
• Reference Types: Anything else. Assignment between values of these types simply causes the location to reference a different object in memory. No copying of values occurs

Arrays are reference types in the CLR and hence do not cause a copying of the underlying value.

Answer 4

Arrays are reference-types, that means that the actual array is instantiated on the heap (presumably by construct_command() ) and the function returns a reference to the array, and it is stored in (the local variable) sData.

So this is not really about memory semantics (the returned value could be null) but about the copy-semantics of reference types. The situation is totally equal to, for instance:

StreamReader reader = System.IO.File.OpenText(filename);

To put it a little more bluntly: You cannot pass an array in .Net at all, you can only pass, copy and assign references to arrays.

Answer 5

Array is a reference type hence only reference is copied. There is No content manipulation.

Answer 6

sData would point to the array returned by construct_command.