Min behaves differently

whatta / linqbridge

Automatically exported from code.google.com/p/linqbridge

Other

0 stars 0 forks source link

Min behaves differently #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Please consider following two expressions and their outputs:

new string[] { "a", null}.Min()
// "a" in System.Core
// null in LinqBridge

new string[] {}.Min()   // or .Max()
// null in System.Core
// exception in LinqBridge

Original issue reported on code.google.com by mrdont@mail.ru on 4 Feb 2011 at 7:34

GoogleCodeExporter commented 9 years ago

I'd better prefer your implementation with aggregation, but the only thing we 
can fix is LinqBridge, not System.Core :)

Original comment by mrdont@mail.ru on 4 Feb 2011 at 7:36

GoogleCodeExporter commented 9 years ago

Original comment by azizatif on 4 Feb 2011 at 10:29

Changed state: Accepted
Added labels: Milestone-Release1.3

GoogleCodeExporter commented 9 years ago

Original comment by azizatif on 4 Feb 2011 at 10:29

GoogleCodeExporter commented 9 years ago

Fixed in r253.

Original comment by azizatif on 4 Feb 2011 at 10:49

Changed state: Fixed