> On Jun 6, 2016, at 3:06 PM, G B via swift-users <swift-users@swift.org> wrote:
>
> Is progress being made on the type checker to get the compiler to stop
> whinging about the complexity of expressions?
Yes, a lot of cases work much better in Swift 3. You might give these a try in
a nightly build. Please file a bug if you continue to see this in Swift 3
though.
-Joe
>
> I can’t really trim down the full project to isolate a good test case, but
> I’m getting a compiler error on this line of code:
> let v=T.Vector4Type([axis[0]*s, axis[1]*s, axis[2]*s, cos(a/2.0)])
>
>
> Interestingly, this line compiled fine (everything is the same except the
> last list element is moved to the front):
> let v=T.Vector4Type([cos(a/2.0), axis[0]*s, axis[1]*s, axis[2]*s])
>
>
>
> The initializer that this code is embedded in is this:
> public init(axis:T.Vector3Type, angle a:T){
> let s=sin(a/2.0)
> let v=T.Vector4Type([axis[0]*s, axis[1]*s, axis[2]*s, cos(a/2.0)])
> let l=v.length()
> self.init(v/l)
> }
>
> I’m running this in a playground, I don’t know if that makes a difference.
>
> I’m willing to wait a little longer for the complier to do its job if it
> means I don’t have to break my code down to one operation per line.
> _______________________________________________
> 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
