I know, I know... Eric Lippert&#39;s answer to this kind of question is usually something like &quot;*because it wasn&#39;t worth the cost of designing, implementing, testing and documenting it*&quot;.

But still, I&#39;d like a better explanation... I was reading [this blog post about new C# 4 features][1], and in the section about COM Interop, the following part caught my attention :

&gt; By the way, this code uses one more new feature: indexed properties (take a closer look at those square brackets after Range.) **But this feature is available only for COM interop; you cannot create your own indexed properties in C# 4.0**.

OK, but why ? I already knew and regretted that it wasn&#39;t possible to create indexed properties in C#, but this sentence made me think again about it. I can see several good reasons to implement it :

- the CLR supports it (for instance, `PropertyInfo.GetValue` has an `index` parameter), so it&#39;s a pity we can&#39;t take advantage of it in C#
- it is supported for COM interop, as shown in the article (using dynamic dispatch)
- it is implemented in VB.NET
- it is already possible to create indexers, i.e. to apply an index to the object itself, so it would probably be no big deal to extend the idea to properties, keeping the same syntax and just replacing `this` with a property name

It would allow to write that kind of things :

    public class Foo
    {
        private string[] _values = new string[3];
        public string Values[int index]
        {
            get { return _values[index]; }
            set { _values[index] = value; }
        }
    }

Currently the only workaround that I know is to create an inner class (`ValuesCollection` for instance) that implements an indexer, and change the `Values` property so that it returns an instance of that inner class.

This is very easy to do, but annoying... So perhaps the compiler could do it for us ! An option would be to generate an inner class that implements the indexer, and expose it through a public generic interface :

    // interface defined in the namespace System
    public interface IIndexer&lt;TIndex, TValue&gt;
    {
        TValue this[TIndex index]  { get; set; }
    }

    public class Foo
    {
        private string[] _values = new string[3];
        
        private class &lt;&gt;c__DisplayClass1 : IIndexer&lt;int, string&gt;
        {
            private Foo _foo;
            public &lt;&gt;c__DisplayClass1(Foo foo)
            {
                _foo = foo;
            }
        
            public string this[int index]
            {
                get { return _foo._values[index]; }
                set { _foo._values[index] = value; }
            }
        }
        
        private IIndexer&lt;int, string&gt; &lt;&gt;f__valuesIndexer;
        public IIndexer&lt;int, string&gt; Values
        {
            get
            {
                if (&lt;&gt;f__valuesIndexer == null)
                    &lt;&gt;f__valuesIndexer = new &lt;&gt;c__DisplayClass1(this);
                return &lt;&gt;f__valuesIndexer;
            }
        }
    }

But of course, in that case the property would *actually* return a `IIndexer&lt;int, string&gt;`, and wouldn&#39;t really be an indexed property... It would be better to generate a real CLR indexed property.

What do you think ? Would you like to see this feature in C# ? If not, why ?

  [1]: http://blogs.msdn.com/csharpfaq/archive/2010/04/12/get-ready-for-c-4-0.aspx



All Indexed Properties Solutions on Gang of Coders

Total of 1 Indexed Properties Solutions

Why C# doesn't implement indexed properties?