Collections... Suggestion for next framework.

[Anibal David Acosta F.]

Currently is not possible to remove and item while iterating between them,
so ...

I suggest something like this..

foreach (MyType CurrentItem in MyCollection)
{
MyCollection.Mark(CurrentItem);
}

MyCollection.RemoveMarkedItems();

[Frank Rizzo]

Anibal David Acosta F. wrote:

Currently is not possible to remove and item while iterating between them,
so ...

I suggest something like this..

foreach (MyType CurrentItem in MyCollection)
{
MyCollection.Mark(CurrentItem);
}

MyCollection.RemoveMarkedItems();

I second the motion.

[Morten Wennevik]

Hi,

Although this does not add much functionality you can't do with a for loop
I would probably use this feature if it existed.

You can suggest features to microsoft using their product feedback center

Search the feature(or bug) on this page and if the feature/bug is not
found or does not apply to your problem you can deliver a new report

http://connect.microsoft.com/feedbac...spx?SiteID=210

Note though that the features of .net 3 has more or less been decided by
now.

On Thu, 17 Aug 2006 04:57:35 +0200, Anibal David Acosta F. <[e-mail]
wrote:

Currently is not possible to remove and item while iterating between
them,
so ...

I suggest something like this..

foreach (MyType CurrentItem in MyCollection)
{
MyCollection.Mark(CurrentItem);
}

MyCollection.RemoveMarkedItems();

--
Happy Coding!
Morten Wennevik [C# MVP]

[Marc Gravell]

Firstly, foreach only currently uses the IEnumerable / IEnumerable<T>
interface, so you'd need to declare such usage in a super-interface. After
all, not all such lists are writeable.

This type of usage would be a pain thread wise - you'd need to be damned
sure that nobody else was using .Mark() [which, OK, you need to watch for
anyway as the iterator will barf], plus note you would need a
..ResetMarkings() at the start in case another caller didn't complete (after
marking a few). By the time you've done that why not just have done with it
and use your own List<Tor whatever to store the marked items, and remove
them in a separate block afterwads? I'm not sure it really adds any more
code...

Perhaps this could be solved by an overload to RemoveAll() (for List<T>; new
for Collection<T>) that accepted an IEnumerable<T>? But then you couldn't
add this to IList<Tor ICollection<Twithout it being a breaking change,
so you'd need another new interface... etc.

All in all, I'm not sure it would be worth the extra complexity. Just my
tuppence.

Marc