That's worrisome. type is such a common identifier that I worry its going to break a lot of code, create some confusion and force the un-esthetic qualifying.
> On 19 May 2017, at 21:38, Slava Pestov via swift-users > <swift-users@swift.org> wrote: > > Do you have a member named ‘type’ in the current scope? > > We changed the behavior of type(of:) so that it behaves like a normal > declaration in the Swift module instead of a special keyword. Unfortunately > this means if you have a ‘type’ already visible in scope, you have to fully > qualify Swift.type(of:). > > Slava > >> On May 19, 2017, at 11:18 AM, Edward Connell via swift-users >> <swift-users@swift.org> wrote: >> >> When running the compiler using the "-swift-version 4" flag, the compiler >> complains about creating a dynamic type. Errors are flagged from within >> concrete base classes and also within protocol extensions. >> >> error: cannot invoke 'type' with an argument list of type '(of: Self)' >> let newObject = type(of: self).init() >> >> Has this changed?? Are we supposed to create dynamic types a different way >> now? >> >> Thanks, Ed >> _______________________________________________ >> 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
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
