Is it possible that the enclosing scope exposes a definition of min that might
take precedence over Swift.min unless you namespace the invocation?
> On 23 Jan 2017, at 14:58, J.E. Schotsman via swift-users
> <swift-users@swift.org> wrote:
>
> This doesn’t compile:
>
> let data1 = Data(count:4)
> let data2 = Data(count:5)
> for i in 0..<min( data1.count, data2.count ) {..} // ! “extra argument in
> call"
>
> I have to write
>
> for i in 0..<Swift.min
>
> Compiler bug?
>
> Jan E.
> _______________________________________________
> swift-users mailing list
> swift-users@swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users
