Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-06 Thread Mark Lacey via swift-evolution
> On Jun 6, 2017, at 3:16 PM, Jens Persson wrote: > > Here are the four you asked me to report: > > https://bugs.swift.org/browse/SR-5127 > Single-tuple and multiple-argument function types should not be considered > equal > >

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-06 Thread Jens Persson via swift-evolution
Here are the four you asked me to report: https://bugs.swift.org/browse/SR-5127 Single-tuple and multiple-argument function types should not be considered equal https://bugs.swift.org/browse/SR-5128 Don't allow swapping a single-tuple function with a multiple-argument function

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-06 Thread Vladimir.S via swift-evolution
On 06.06.2017 19:41, Mark Lacey wrote: On Jun 6, 2017, at 4:00 AM, Vladimir.S > wrote: Mark, could you please also comment this inconsistencies / bugs : (swift-4.0-DEVELOPMENT-SNAPSHOT-2017-06-01-a-osx) func fooParam(_ x: Int, _ y: Int){} func

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-06 Thread Mark Lacey via swift-evolution
> On Jun 6, 2017, at 4:00 AM, Vladimir.S wrote: > > Mark, could you please also comment this inconsistencies / bugs : > (swift-4.0-DEVELOPMENT-SNAPSHOT-2017-06-01-a-osx) > > func fooParam(_ x: Int, _ y: Int){} > func fooTuple(_ x: (Int, Int)) {} > > print("type of fooParam

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-06 Thread Vladimir.S via swift-evolution
Mark, could you please also comment this inconsistencies / bugs : (swift-4.0-DEVELOPMENT-SNAPSHOT-2017-06-01-a-osx) func fooParam(_ x: Int, _ y: Int){} func fooTuple(_ x: (Int, Int)) {} print("type of fooParam is", type(of:fooParam)) // result: type of fooParam is (Int, Int) -> () print("type

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-06 Thread Mark Lacey via swift-evolution
> On Jun 6, 2017, at 12:08 AM, Jens Persson via swift-evolution > wrote: > > IMHO There seems to be a lot of bugs and inconsistencies left in more than > just the reflective type system, for example the following won't compile > although the two foo funcs clearly

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-06 Thread Jens Persson via swift-evolution
IMHO There seems to be a lot of bugs and inconsistencies left in more than just the reflective type system, for example the following won't compile although the two foo funcs clearly take different types as argument: func foo(fun: (Int, Int) -> ()) { print("was given a function of type: (Int,

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-05 Thread John McCall via swift-evolution
> On Jun 5, 2017, at 12:08 AM, Jens Persson via swift-evolution > wrote: > So the bug in the reflective type system needs to be fixed before SE-0110 can > actually be implemented (so that the statements in its title and text are > true when compared to the actual

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-05 Thread Jens Persson via swift-evolution
So the bug in the reflective type system needs to be fixed before SE-0110 can actually be implemented (so that the statements in its title and text are true when compared to the actual behavior of the current Swift 4 compiler), And yet: 1. The status of SE-0110 is "Implemented" 2. These

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-04 Thread Ben Rimmington via swift-evolution
I assumed that Swift 3 mode would be the default, so that existing `#!/usr/bin/swift` scripts continue to work. -- Ben > On 3 Jun 2017, at 23:47, Jens Persson wrote: > > Yes of course, try my demonstration code yourself. > (In the current dev snapshots, -swift-version 4 is

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-03 Thread John McCall via swift-evolution
> On Jun 3, 2017, at 3:01 PM, Jens Persson via swift-evolution > wrote: > I was notified that my SR-2216 and SR-296 had been "fixed as part of > implementing SE-0110". > > But AFAICT SE-0110 can't possibly be fully implemented in dev snapshot > 2017-06-02, even

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-03 Thread Jens Persson via swift-evolution
Yes of course, try my demonstration code yourself. (In the current dev snapshots, -swift-version 4 is the default and -swift-version 3 is what you need to set if you want 3 compability) On Sun, Jun 4, 2017 at 12:37 AM, Ben Rimmington wrote: > Are you using the Swift 4

Re: [swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-03 Thread Ben Rimmington via swift-evolution
Are you using the Swift 4 language mode? -- Ben > On 3 Jun 2017, at 23:01, Jens Persson wrote: > > I was notified that my SR-2216 and SR-296 had been "fixed as part of > implementing SE-0110". > > But AFAICT SE-0110

[swift-evolution] Why is the status of SE-0110 "implemented"?

2017-06-03 Thread Jens Persson via swift-evolution
I was notified that my SR-2216 and SR-296 had been "fixed as part of implementing SE-0110". But AFAICT SE-0110 can't possibly be fully implemented in dev snapshot 2017-06-02, even though the status of SE-0110 is "Implemented (Swift 4)". The title of SE-0110 is "Distinguish between single-tuple