Question

So this works..

public MyClass(ref Apple apple)
{
    apple = new Apple("Macintosh"); // Works fine
}

But is it possible to do something like this?

private Apple myApple;

public MyClass(ref Apple apple)
{
    myApple = apple;
}

public void ModifyApple()
{
    myApple = new Apple("Macintosh"); // does not change the input variable like the first example did
}

When the ref variable is copied to the member variable myApple it appears to lose it’s ‘ref-ness’ and re-assigning it no longer changes the input variable. Is there a way around this?

Answer 1

Not really, no. By the time your code is next invoked, the original variable used as the method argument may no longer even exist:

void Foo()
{
    MyClass x = Bar();
    x.ModifyApple();
}

MyClass Bar()
{
    Apple apple = new Apple();
    return new MyClass(ref apple);
}

Here, apple is a local variable, in a stack frame which will have been popped by the time we call ModifyApple.

Are you sure you need to modify the original caller’s variable rather than just changing the object itself?

One way to sort of fake this would be to use a wrapper type to start with:

public class MutableWrapper<T>
{
    public T Value { get; set; }
}

Then pass in a MutableWrapper<Apple>, and store that in your class. Then in ModifyApple you can write:

wrapper.Value = new Apple();

This won’t change the caller’s variable, but next time the caller looks at the Value property, they’ll see your new apple.

To be honest, this sort of thing tends to make for hard-to-maintain code, and even ref isn’t great for readability. If you can explain the bigger picture of what you’re trying to achieve, we may be able to suggest a better overall approach.