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
It's shorter, more succinct and in my opinion, just nicer.
This is technically a breaking change if someone is using a collection type which implements IEnumerable<T> but not ICollection<T>. All the code I've seen both in samples and in the wild always seems to use List<T>, which does implement ICollection<T>.
This should be expanded not just the To address but to any other collection type, and probably looked at beyond EmailMessage.
Thoughts?
The text was updated successfully, but these errors were encountered:
Which implement
IEnumerable<T>
toICollection<T>
with new'd up empty collections on instantiation.Rationale; typical current usage:
Versus new API available...
It's shorter, more succinct and in my opinion, just nicer.
This is technically a breaking change if someone is using a collection type which implements
IEnumerable<T>
but notICollection<T>
. All the code I've seen both in samples and in the wild always seems to useList<T>
, which does implementICollection<T>
.This should be expanded not just the
To
address but to any other collection type, and probably looked at beyondEmailMessage
.Thoughts?
The text was updated successfully, but these errors were encountered: