You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see that someone has created an issue two years ago, and I think it is important, because it is difficult to convert a List<int> or ObservableCollection<int> to IEnumerable<object>, but they are easy to be converted to IEnumerable. If the type of GridView.DataStore is changed to IEnumerable, we can remove the limitation of where T: class in GridView<T>, and it is obviously more convenient.
The text was updated successfully, but these errors were encountered:
Expect that it is a broken change, I don't see any downsides. It doesn't require programmers to change the code, because if the instance of a type is assignable to IEnumerable<obejct>, it is certainly assignable to IEnumerable. By the way, WPF, UWP and Avalonia all use IEnumerable.
I see that someone has created an issue two years ago, and I think it is important, because it is difficult to convert a
List<int>
orObservableCollection<int>
toIEnumerable<object>
, but they are easy to be converted toIEnumerable
. If the type ofGridView.DataStore
is changed toIEnumerable
, we can remove the limitation ofwhere T: class
inGridView<T>
, and it is obviously more convenient.The text was updated successfully, but these errors were encountered: