Issue 19 in linqbridge: Min behaves differently

[linqb...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 19 by ilya.ind...@gmail.com: Min behaves differently
http://code.google.com/p/linqbridge/issues/detail?id=19

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

[linqb...@googlecode.com]

Comment #1 on issue 19 by ilya.ind...@gmail.com: Min behaves differently
http://code.google.com/p/linqbridge/issues/detail?id=19

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

[linqb...@googlecode.com]

Updates:
Status: Accepted
Labels: Milestone-Release1.3

Comment #2 on issue 19 by azizatif: Min behaves differently
http://code.google.com/p/linqbridge/issues/detail?id=19

(No comment was entered for this change.)

[linqb...@googlecode.com]

Updates:
Owner: azizatif

Comment #3 on issue 19 by azizatif: Min behaves differently

[linqb...@googlecode.com]

Updates:
Status: Fixed

Comment #4 on issue 19 by azizatif: Min behaves differently
http://code.google.com/p/linqbridge/issues/detail?id=19#c4

Fixed in r253.