3 ms·
OOOH I was so wanting to tell the OP What is so hard about this??? //assume some sorta IEnumerable derivitive IEnumerable<foo> bar = new IEnumerable<foo>() { o
by S_A_P 16y ago
OOOH I was so wanting to tell the OP
What is so hard about this???
//assume some sorta IEnumerable derivitive
IEnumerable<foo> bar = new IEnumerable<foo>() { obj1, obj2, obj3, obj4, ...};
var accumulator = bar.TakeWhile(x => x.property == someValue);
but then I saw the .NET 2.0 timeframe.
But even with .NET 2 you had generics which makes things pretty easy. But then again, he/she is ranting so I should just ignore him/her.
It doesn't matter what language you are using, if you cant write something that is legible to solve the problem, think about it more.
- InclinedPlane 16y agoI suspect they were using .NET 1.x at the time, which would explain a lot.
- S_A_P 16y agoI initially thought that as well, but the post did mention generics.
- fhars 16y agoIf you had read the article you would have noticed that using generics the way they were intended to solve this problem was what he was called out for by his manager.