是否可以在 C# 中创建一个公共方法来生成未知数量的私有实例变量？

Question

Basically I am trying to implement my own array class, and I was wondering if creating a public method that generates an unknown number of private instance variables was the way to go? Something like:

public class myArray {
    public myArray(int length) {
        for(int i = 0; i < length; i++) {
            int component+i;
        }
    }
    int component(int indexOfComponent) {
        return component+indexOfComponent; 
    }
}

I know the the line of code inside that for loop makes no sense. But I just thought I would illustrate what I was talking about. What would result from creating an object from the myArray class with 3 as the constructor parameter would be:

public class myArray {
    private int component1;
    private int component2;
    private int component3;

    public myArray(int length) {
        for(int i = 0; i < length; i++) {
            int component+i;
        }
    int component(int indexOfComponent) {
            return component+indexOfComponent; 
        }
    }
}

And I know those variables would only exist inside the for loop, but that is the best way I can exemplify what I am trying to do. Is this even the way to go if I am trying to implement my own array class? Also; there's one more thing about this that I think may deserve a separate question but it's the whole problem with naming variables dynamically with a for loop.

Answer 1

Basically I am trying to implement my own array class

I'd urge you not to do that.

I was wondering if creating a public method that generates an unknown number of private instance variables was the way to go

No. The variables need to known at compile-time .

The "way to go" is to use an array or another existing collection type.

Fundamentally you can't implement arrays directly in C#. Arrays and strings are the only objects where the size of an instance varies from object to object. For everything else, the layout is the same for every object.

(As mentioned in comments, you could dynamically create a new type for each instance using Reflection.Emit or something similar, but you really really don't want to do that.)