Hi Dess,

Your examples are not really correct. Before this change, your examples worked exactly the same way. When you use var, object is assumed. Of course the object contains a GridViewCellInfo, but you have to cast it first to use one of its members.

The goal of my suggestion was to prevent unnecessary casts. This change didn't do that.

You said: " However, please have in mind that we are not planning to make any further changes in the collection since it affects all our customers that use RadGridView"

We already had that discussion before in the support ticket 1570683 leading up to this request. I asked you "So if you can find me one software example which will break after implementing IEnumerable<T>, then I will have learned something new today. I would love that :)"

I think that question was the one that changed your mind and you created this feature request.

 

 

I have just update my Telerik library to version 2022.3.913.48.

In here it looks like GridViewCellInfoCollection has implemented IEnumerable<T>. But it has been implemented the wrong way:

• The not-generic IEnumerable should be implemented explicitly.
• The generic IEnumerable<T> should be implemented implicitly.

Right now it is the other way around. As a result, a foreach(var cell in GridViewCellInfoCollection) will still result in objects, not GridViewCellInfo.

Hi Dess,

Thanks again for your fast replies. Of course I understand you will make the final decision based on customers' wishes. Although I cannot imagine any customer who prefers (unnecessary / manual) boxing/casting over generic interfaces. :)

Regards,

Martin

As requested in support ticket 1570683, I have made a list of suggestions to implement generic interfaces. I have made this list based on a little piece of software which used reflection to see if there is a relatively good match between your collections and generic interfaces. See attachment.