Re: [swift-users] Why inout protocol parameter in function work with strange

I think you're missing the underlying semantic problem here: func transform(item: inout Position) { item = Airplane() } var car = Car(x: 50) var pos: Position = car move(item: ) // this works, but 'pos' is now an Airplane move(item: ) // this doesn't work because 'car' has to stay a Car Dave

Re: [swift-users] Why inout protocol parameter in function work with strange

Because generic uses `Car` instead of `Position` when running the code, so there is no casting as `car as Position` as in your original code. The `T:Position` part restricts that the type conforms `Position`, but it won't use `Position`, it uses the type. Zhaoxin On Sat, May 27, 2017 at 4:58 PM,

Re: [swift-users] Why inout protocol parameter in function work with strange

Thanks. Why generic function don not require memory allocate for inout variable, even if it is protocol type? >Пятница, 26 мая 2017, 19:35 +03:00 от Guillaume Lessard >: > >In your example, the compiler needs a parameter of type Position. Car is a >type of

Re: [swift-users] Why inout protocol parameter in function work with strange

In your example, the compiler needs a parameter of type Position. Car is a type of Position, but they are not interchangeable. See below: > On May 26, 2017, at 00:33, Седых Александр via swift-users > wrote: > > protocol Position { > var x: Double { getset } > } >